[erlang-questions] Make application a dependency, but don't start it?

David Welton <>
Mon Dec 1 16:44:19 CET 2014


Does

  {mochiweb, load},

in relx.config work?

Like:

% Generated by update_version.sh from relx.config.in
{release, {gsd_web, "0.6.2"},
 %% A lot of these should probably be relocated to the .app.src
 %% "applications" section for whatever depends on them.
 [
  cowboy,
  lager,
  lager_syslog,
  {mimetypes, load},
  {mochiweb, load},
  {observer, load},
...

On Mon, Dec 1, 2014 at 4:39 PM, Roger Lipscombe <> wrote:
> I'm in need of a short-term hack where I have applications A and B. I
> need to make the beam files from B available to A when building my
> release, but I *don't* want to start B.
>
> I'm using relx.
>
> Unfortunately, B is a non-library application -- it has a {mod, {Mod,
> Args}} term in its .app file; I can't change this.
>
> If I add B to A.app.src, then relx includes it in the boot script and starts it.
> If I add B to A/relx.config as a goal of the release, the same happens.
>
> How can I make a release of A that includes B without
> application:start(B) being called?
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions



-- 
David N. Welton

http://www.welton.it/davidw/

http://www.dedasys.com/


More information about the erlang-questions mailing list