<div>
Was guessing that was the answer - I'll give it a go...
</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 Friday, 16 August 2013 at 16:42, Loïc Hoguin wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>Well I'm sure if you create a base Makefile (without erlang.mk) that </div><div>exports DEPS_DIR and then call $(MAKE) on all folders in /apps (which </div><div>would themselves contain Makefiles that use erlang.mk), it would work </div><div>just fine. You can still keep only one erlang.mk in your repos and use </div><div>include ../../erlang.mk instead for example.</div><div><br></div><div>But know that this folder structure is a rebar thing and not standard </div><div>(just like /deps you'll say, but that one is insanely useful regardless </div><div>of the project structure otherwise).</div><div><br></div><div>On 08/16/2013 02:27 PM, Steve Strong wrote:</div><blockquote type="cite"><div><div>Looks good - I like simple! Quick question, does it support multiple</div><div>applications, for example a project laid out as:</div><div><br></div><div>/proj</div><div>/deps</div><div>/stuff</div><div><br></div><div>/apps</div><div>/app1</div><div>/app2</div><div><br></div><div>Most of our stuff is in that form, with shared dependencies between the</div><div>various apps. Rebar is quite happy with that format, but I can't see</div><div>how to persuade erlang.mk to handle that.</div><div><br></div><div>Cheers,</div><div><br></div><div>Steve</div><div><br></div><div>--</div><div>Steve Strong</div><div>Sent with Sparrow <<a href="http://www.sparrowmailapp.com/?sig">http://www.sparrowmailapp.com/?sig</a>></div><div><br></div><div>On Thursday, 15 August 2013 at 16:19, Loïc Hoguin wrote:</div><div><br></div><blockquote type="cite"><div><div>Hello friendly people,</div><div><br></div><div>I would like to make an official announcement of erlang.mk now that all</div><div>the features I wanted are in.</div><div><br></div><div>erlang.mk is a rebar replacement. It was initially created for allowing</div><div>a faster development process than rebar and for better compatibility</div><div>with Linux build tools. It should work on Linux and OSX with GNU Make</div><div>installed.</div><div><br></div><div>Projects using erlang.mk are still compatible with rebar. Dependencies</div><div>fetched by rebar are stored in the same deps/ directory, and projects</div><div>using erlang.mk can still be used as rebar dependencies, with or without</div><div>a rebar.config file.</div><div><br></div><div>erlang.mk also features a simple package index. Try `make pkg-list` to</div><div>list all packages currently available. All the packages listed are</div><div>compatible with erlang.mk with no tweaking required.</div><div><br></div><div>Makefiles written with erlang.mk are *VERY* simple, here are two examples:</div><div><br></div><div>* <a href="https://github.com/extend/farwest/blob/master/Makefile">https://github.com/extend/farwest/blob/master/Makefile</a></div><div>* <a href="https://github.com/extend/cowboy/blob/master/Makefile">https://github.com/extend/cowboy/blob/master/Makefile</a></div><div><br></div><div>I wrote about erlang.mk and relx recently on the Nine Nines blog.</div><div>erlang.mk is the perfect companion to relx.</div><div><br></div><div>* <a href="http://ninenines.eu/articles/erlang.mk-and-relx">http://ninenines.eu/articles/erlang.mk-and-relx</a></div><div><br></div><div>Here are examples of projects that are using and compatible with</div><div>erlang.mk:</div><div><br></div><div>* <a href="https://github.com/jlouis/etorrent">https://github.com/jlouis/etorrent</a></div><div>* <a href="https://github.com/extend/cowboy">https://github.com/extend/cowboy</a></div><div>* <a href="https://github.com/extend/farwest">https://github.com/extend/farwest</a></div><div><br></div><div>You can find erlang.mk at the following URL:</div><div><br></div><div>* <a href="https://github.com/extend/erlang.mk">https://github.com/extend/erlang.mk</a></div><div><br></div><div>Contributions to the package index are of course welcome! The only</div><div>requirement is that the package is to be compatible with erlang.mk</div><div>itself. Just send a PR to the erlang.mk project updating the</div><div>packages.v1.txt!</div><div><br></div><div>Enjoy!</div><div><br></div><div>--</div><div>Loïc Hoguin</div><div>Erlang Cowboy</div><div>Nine Nines</div><div><a href="http://ninenines.eu">http://ninenines.eu</a></div><div>_______________________________________________</div><div>erlang-questions mailing list</div><div>erlang-questions@erlang.org <<a href="mailto:erlang-questions@erlang.org">mailto: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></blockquote><div><br></div><div><br></div><div>-- </div><div>Loïc Hoguin</div><div>Erlang Cowboy</div><div>Nine Nines</div><div><a href="http://ninenines.eu">http://ninenines.eu</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>