Just found out that rebar supports "raw" repositories[1] which will only be <div>fetched but ignored during compilation. So after running `get-deps`, I </div><div>had to manually compile deps/exmpp and now I `rebar compile` works fine.</div>
<div><br></div><div>Looks like my problem is solved!</div><div><br></div><div>Thanks</div><div><br></div><div>[1] <a href="https://github.com/rebar/rebar/blob/master/rebar.config.sample#L160-L175">https://github.com/rebar/rebar/blob/master/rebar.config.sample#L160-L175</a></div>
<div><br><div><br><div class="gmail_quote">On Fri, Dec 7, 2012 at 8:18 PM, Garrett Smith <span dir="ltr"><<a href="mailto:g@rre.tt" target="_blank">g@rre.tt</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Fri, Dec 7, 2012 at 8:32 AM, Vineet Naik <<a href="mailto:naikvin@gmail.com">naikvin@gmail.com</a>> wrote:<br>
> Hi Garrett,<br>
><br>
> On Fri, Dec 7, 2012 at 7:40 PM, Garrett Smith <<a href="mailto:g@rre.tt">g@rre.tt</a>> wrote:<br>
>><br>
>> [...]<br>
>><br>
>><br>
>> At build time, rebar will download and build dependencies in a local<br>
>> "deps" dir.<br>
><br>
><br>
> Does it require that the dependencies be rebar compatible as well. Right<br>
> now I am having exmpp which doesn't use rebar and I guess doesn't have<br>
> the directory structure suitable for it.<br>
<br>
</div>Briefly looking at this, you'll have a problem following my advice<br>
with rebar for this case -- that project has a complex build.<br>
<br>
I spotted this thread:<br>
<br>
<a href="https://support.process-one.net/browse/EXMPP-51" target="_blank">https://support.process-one.net/browse/EXMPP-51</a><br>
<br>
which points to this project:<br>
<br>
<a href="https://github.com/archaelus/exmpp" target="_blank">https://github.com/archaelus/exmpp</a><br>
<br>
I tried building that using "rebar compile" but hit some errors.<br>
<br>
If that works for you, just list that fork for your rebar dependency.<br>
Otherwise, you could troubleshoot the problem or, just build the<br>
project yourself using whatever works from a Makefile -- and put it<br>
into a local "deps" dir. Other required apps will land there from<br>
rebar builds and you'll have a single dir for ERL_LIBS.<br>
<br>
As for building a release, it sounds like rebar has come of age. But<br>
exmpp may not be friendly. Could be a good area to help contribute to<br>
with patches.<br>
<div class="im"><br>
> With exmpp installed in default erlang search path, it's not an issue for<br>
> me at least during development but frankly I would be more happy with a<br>
> sandboxed environment similar to Python's virtualenv. Glad that rebar<br>
> downloads and builds dependencies local to the project. Will try if it works<br>
> for non-rebar-compatible libs too.<br>
><br>
> Thanks for your reply, it helped a lot :-)<br>
<br>
</div>You're welcome!<br>
<span class="HOEnZb"><font color="#888888"><br>
Garrett<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Vineet Naik<br><br><br>
</div></div>