building applications stored in an "apps" subfolder

OJ Reeves oj at buffered.io
Fri Oct 8 07:22:49 EDT 2010


Thanks Andrew! For some reason I was under the impression that if I went
down the route of using sub_dirs i'd have to deal with the dependencies in
the same manner as well. That made me think I was doing something wrong.

I should have just tried it!

Cheers!
OJ


On Fri, Oct 8, 2010 at 9:11 PM, Andrew Tunnell-Jones <andrew at tj.id.au>wrote:

> On 08/10/2010, at 9:42 PM, OJ Reeves wrote:
>
> I have two questions:
>
>
>    1. Is it a good idea to move individual applications into their own
>    folder inside an apps subfolder like I have shown above? Is that what Erlang
>    projects do in general? Should I have left it as I had it before where the
>    top level application because the compile entry-point for the entire system?
>
> I've seen a couple of projects built in that style. Whether it makes sense
> is a mix pragmatism and personal preference. In my own project I've broken
> out generic apps into deps and kept apps that are only useful in the context
> of the project in the apps folder.
>
>
>    1. If this is the right approach, how do I get rebar to build each of
>    the applications in the "apps" folder individually as if I had called make
>    from their respective directories?
>
> Adding the following to your rebar.config should do the job:
>
> {sub_dirs, ["apps/app1", "apps/apps2"]}.
>
> Cheers,
>
> — Andrew
> http://andrew.tj.id.au/
>
>


-- 

OJ Reeves
http://buffered.io/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/rebar_lists.basho.com/attachments/20101008/5d7b17f1/attachment.html>


More information about the rebar mailing list