Browse files

removed thrift_erl from retool.config.. manually copying

  • Loading branch information...
1 parent 13e0e40 commit 4f9a22cf7f61576c630caedc4c52256b8441350d @xslogic committed Nov 8, 2010
Showing with 2 additions and 2 deletions.
  1. +2 −1 generate
  2. +0 −1 rel/reltool.config
@@ -1,11 +1,12 @@
rebar get-deps
cd deps/thrift_erl
rebar compile
+rebar generate
cd -
rebar compile
rm -rf rel/phoebus
rm -rf deps/thrift_erl/rel/thrift_erl
rebar generate
-cp deps/thrift_erl/rel/thrift_erl/lib/thrift_erl-0.5.0.ez rel/phoebus/lib/
+cp -r deps/thrift_erl/rel/thrift_erl/lib/thrift_erl* rel/phoebus/lib/
chmod +x ./rel/phoebus/bin/phoebus
./rel/phoebus/bin/phoebus co
@@ -5,7 +5,6 @@
- thrift_erl,
{rel, "start_clean", "",

3 comments on commit 4f9a22c

I believe rebar actually uses the reltool.config to check that all the components are correctly setup in the rel folder. So by removing this you choose not to use rebar added safety.


xslogic replied Nov 9, 2010

hey stewart..

yeah.. thats y i had put it in there initially... but for some reason, rebar was behaving kind of weird..
a couple of people had mailed me and said that "rebar generate" at the top level was failing because rebar could not recognize "thrift_erl" to be a valid app.
It was funny cuz, it used to work fine for me... but sometimes when I pull a fresh clone and run generate, rebar spits out :

==> rel (generate)
{"init terminating in do_boot","Release phoebus uses non existing application thrift_erl"}

Actually I guess it has something to do with the way rebar spawns of the reltool server when there are dependencies.. I am guessing the top level server should be spawned only after the reltool server for all dependencies have finished.. Am in the process of digging into rebar code to verify this.. till I figure it out, I guess ill do this stuff manually..

Had mailed @dizzyd with regard to this.. he said he'll take a look..


all is made clear :)

Please sign in to comment.