I do not see a facility in Rebar to pass variables through to the command
line after a generate.
The .app file is transient (will be destroyed and rebuilt on a clean), and
generating nodes kinda needs -f which blows stuff away there too.
I need to pass an option to gproc to turn on gproc_dist and
Can't you have something in your src directory like
foo.app.src
which is what the ebin/foo.app is generated from?
Then you put whatever you want in there?
-Anthony
On Wed, May 18, 2011 at 12:23:20PM -0700, Mike Oxford wrote:
> I do not see a facility in Rebar to pass variables through to the c
Yes, you are correct. I completely forgot about the baseline file.
Back to my hole...and thank you.
-mox
On Wed, May 18, 2011 at 2:11 PM, Anthony Molinaro <
antho...@alumni.caltech.edu> wrote:
> Can't you have something in your src directory like
>
> foo.app.src
>
> which is what the ebin/foo.
Perhaps I spoke too soon. :)
'rebar compile' will nuke the ebin/.app file.
Setting the {env, []} setting inside this file and then generating (or in
the srv/.app.src file) and it does not get passed down to the actual
vm.
{env, [{gproc, "gproc_dist 'all'"}]} does not work
{env, [{gproc, 1}]} do
To close the loop on this for the archives
application:get_all_env() returns [] ...
application:get_all_env() does show the registrations.
{env, []} entries are being set in the
"rel//releases//.script" file.
I'm still working through getting gproc to actually work as gproc_dist but
happily reba
