[erlang-questions] .app(.src) and .appup(.src) files

Loïc Hoguin <>
Fri Feb 7 21:43:48 CET 2014

src/appname.app.src typically doesn't contain the list of modules, which 
is filled in automatically when copying it to ebin/appname.app.

That's the whole point of the .app.src really. I don't think tools do 
much more than that. I think rebar allows you to set {vsn, git} to 
automatically set a version based on the branch/tag/commit/.. but that's it.

On 02/07/2014 09:25 PM, Ivan Uemlianin wrote:
> Dear All
> Looking around at how erlang applications are laid out, especially the
> .app and .appup files.  Some people have them in myapp/ebin/.  Some
> people keep .src versions in myapp/src/ and copy them over to ebin when
> building the app.  Some people are half-and-half.  Tools make
> assumptions accordingly.
> I can see arguments on either side:  keeping .src versions in src/ saves
> you putting ebin/ under version control;  keeping the files in ebin/
> simplifies the build process.  Well, ok, I can see one argument on
> either side.
> Might the files ever be altered when they're moved from src/ to ebin/,
> or are they always just copied verbatim?
> I don't want to start an argument, I'd just like to make an informed
> choice.
> With thanks and best wishes
> Ivan
> _______________________________________________
> erlang-questions mailing list
> http://erlang.org/mailman/listinfo/erlang-questions

Loïc Hoguin

More information about the erlang-questions mailing list