<div>
Feel free to take a look at <a href="https://github.com/id3as/erl-mk">https://github.com/id3as/erl-mk</a> - it’s a work-in-progress, but we are using it on a couple of projects…</div><div><br></div><div>Cheers,</div><div><br></div><div>Steve</div>
<div><div><br></div><div>-- </div><div>Steve Strong</div><div>Sent with <a href="http://www.sparrowmailapp.com/?sig">Sparrow</a></div><div><br></div></div>
<p style="color: #A0A0A8;">On Tuesday, 1 April 2014 at 01:08, Alex Shneyderman wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div><a href="https://github.com/rustyio/BashoBanjo">https://github.com/rustyio/BashoBanjo</a></div><div><a href="https://github.com/sylane/erod">https://github.com/sylane/erod</a></div><div><br></div><div>both use rebar and multi-app setup. The problem that you are bound to</div><div>run into with this setup is the long list of inter-dependent apps. The</div><div>exact list of the apps becomes important as the ones that do not</div><div>depend on anything should percolate to the top and the neediest apps</div><div>should be at the bottom.</div><div><br></div><div>It is possible to come up with a similar structure for erlang.mk +</div><div>relx. But you'd have to do a lot of gnu make hacking before it works</div><div>(for example, the link that Loic posted sidelines the problem of</div><div>inter-dependent apps all-together, I believe; there is a lot more than</div><div>meets the eye). Another problem is some dependencies are built with</div><div>rebar, so some funky versioning schemes that rebar supports and pre</div><div>and post hooks make it hard to live without rebar - erlang.mk can call</div><div>rebar but still you will need rebar for those particular deps.</div><div><br></div><div><br></div><div>On Mon, Mar 31, 2014 at 6:35 PM, t x <<a href="mailto:txrev319@gmail.com">txrev319@gmail.com</a>> wrote:</div><blockquote type="cite"><div><div>To avoid the X-Y problem: I'm not particular attached to erlang.mk + relx.</div><div><br></div><div>I just want a set of tools for "how do I design the directory</div><div>structure of a multiple-app erlang program."</div><div><br></div><div>On Mon, Mar 31, 2014 at 3:31 PM, t x <<a href="mailto:txrev319@gmail.com">txrev319@gmail.com</a>> wrote:</div><blockquote type="cite"><div><div>Hi,</div><div><br></div><div> Can someone please point me to a git hub repo that:</div><div><br></div><div> 1) uses erlang.mk + relx</div><div><br></div><div> 2) has multiple apps</div><div><br></div><div> 3) is an example of directory structure I should copy?</div><div><br></div><div>Thanks!</div><div><br></div><div>Problem: I'm starting to need to refactor my code, and I want to know</div><div>what an idiomatic multiple-app directory structure looks like.</div></div></blockquote><div>_______________________________________________</div><div>erlang-questions mailing list</div><div><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a></div><div><a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a></div></div></blockquote><div>_______________________________________________</div><div>erlang-questions mailing list</div><div><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a></div><div><a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>