rebar ( Dave Smith's Erlang build and packaging tool used by the Nitrogen project ) doesn't seem to work well for Windows at the moment:
lang/erlang/nitrogen>make rel_inets ./rebar get-deps ==> rel (get-deps) ==> nitrogen (get-deps) Pulling nitrogen_core from {git,"https://github.com/nitrogen/nitrogen_core.git", "HEAD"} ERROR: "c:\Program Files (x86)\Git\bin\bash.exe" -c ""c:\Program Files (x86)\Git\bin\git.exe" --version; echo _port_cmd_status_ $?" failed with error: 127 make: *** [get-deps] Error 1
This thread doubts that it works on Windows in general .
This recent irc trasncript mentions:
<Thesolonius>
and creating the app armature creates a bash script that we cannot run.
makes me wonder if our understanding of the correct installation environment is wrong?
in our release the script cannot find " run_erl "
and we cannot find " run_erl " anywhere on the box
the same code works fine on linux
<drev1>
perhaps it should be run_erl.exe/
<Thesolonius>
there is no run_erl.*
<drev1>
oh hmm
<Thesolonius>
there is start_erl.exe
but if this name was a problem, it suggests that the fixture is not aimed at windows
during the generate command?
Which would make me ask if the fixtures can give a hint regarding the current platform?
<drev1>
I'm not sure how much work was done with the fittings on the windows
looks like start_erl is the equivalent of windows run_erl
10:29, but it seems to accept different command line arguments
<Thesolonius>
what we found too
<drev1>
I assume that you will need a template for Windows to generate releases
not the create-node template that comes with the fixture
source share