eclipse-archived
Node.js executable path should be configurable.
Node.js package is not available for all Gnu/Linux distributions. My Node.js installation is in my home directory. Eclipse can't find Node binary when I try to run project as Javascript application. Adding my PATH env. to Run Configuration also didn't work.
You're right that it should be configurable. Does it work if you put it in your PATH though?
It's in my shell PATH variable. I added this env. var. to my launch configuration but this isn't work either.
@decafbad how did you install node.js? What is the name of your executable? It should be node but if you installed from RPM or something similar it maybe different. I need to know so that I can include it in the search if it's not a standard name.
Sorry for delay. I installed Node in /home/mkose/eksoft/nodejs and then added PATH variable to Eclipse run configuration as /home/mkose/eksoft/nodejs/bin. Executable name is node.
Taking it for 1.1. if https://github.com/ceylon/ceylon-js/issues/385 allows using the PATH correctly, setting the PATH environment variable in the launch configuration might be sufficient. I'll check this.
OK so currently adding it to the PATH environment variable in the launch configuration allows finding it, but doesn't allow overriding the default node executable that might already exist in /usr/bin.
However this last point is more a ceylon-js point.
Given the fact that it is possible ti use the PATH environment variable inside the IDE launch configuration, is this issue really a priority for 1.1 ?
@gavinking : wdyt ?
@decafbad : does the PATH variable set in the eclipse launch config work also for you ?
@decafbad : Since we can override the search path, having something better is moved to milestone 1.2. Also because it seems that the JS runner doesn't allow overriding explicitely the full path of the nodeJs command (can you confirm @chochos ?)
The JS run tool allows setting a node-exe property which should point to the node executable. If it's not set then the search is performed.
I remember adding a textfield somewhere in the JS launcher properties where you could set the path to the node executable, and the search was done so if it was found, the path would already show there.