viproma/coral

CORAL_HOME environment variable on windows

Opened this issue · 2 comments

Should we include a CORAL_HOME environment variable on windows which points to the bin folder of a coral distribution? This way we can use coralslaveprovider and coralmaster on the command line from anywhere without the full path, and we don't have to change the PATH environment variable which can be a mess to maintain.

How would this work? Unless I'm misunderstanding what you're asking for, simply defining CORAL_HOME won't make Windows search there for the executables.

It's a good idea for coralslaveprovider to use such an environment variable to locate coralslave.exe, however!

I probably had a brain fart, because I realize now that this won't work as I had intended, #FeelsBadMan.

The main reason for why I had this idea is that I'm currently working on a MATLAB application which uses coral, and in order to use coral I need the path to its bin folder. This can be a pain sometimes so it would be nice to just have a CORAL_HOME environment variable, but since coral doesn't have an installer which can create this environment variable I suppose it's not that great of an idea anyway. I suppose it wouldn't hurt to add functionality that uses a CORAL_HOME environment variable if it exists though.