Closed dantswain closed 11 years ago
Note I'm not requiring percept
or percept2
manually at all. This is coming in through the system somehow; I don't think it's anything specific about my setup.
I tried a bunch of changes to my reltool.config, but no luck. I had to uninstall percept2 (there's no make uninstall
, btw... I had to rm -rf /usr/local/lib/erlang/lib/percept2-1.0
) to make progress. I'll try to revisit later.
Percept2 and Percept do have some common modules, but since you are not requiring Percept or Percept2 manually at all, I don't know why these conflicts were checked. I don't use rebar a lot, so sorry that I'm not very helpful. Thanks for noting there is not 'make uninstall', will add it soon.
I did a bit of research and I believe reltool, under default circumstances, will try to include every module in the system directories (i.e., every app in /usr/local/lib/erlang/lib/
). I don't think this is a rebar-specific issue because that decision gets made in the reltool code.
I can understand that you might think this is not a bug with Percept2, but installing Percept2 rendered my entire build system unusable. The solution might be as simple as modifying the documentation to point out how the user needs to modify their release config.
If I have some time I'll try to figure out what the right thing to do is. It's interesting to try to understand how reltool works ;)
Thanks! I would be great if this could be resolved.
{sys, [ ....
success to rebar generate,
I'm building a project with rebar and get the following error on
rebar generate
:I installed percept2 on my system (OS X, erlang R16B01) by cloning this repo and doing
My reltool.config file:
I'm looking into this. If I can find a fix, I'll submit a pull request.