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

Tristan Sloughter <>
Mon Dec 1 16:43:53 CET 2014


In relx.config do:

{release, {<name>, <version>}, 
    [A, 
     {B, load}]}.

-- 
  Tristan Sloughter
  

On Mon, Dec 1, 2014, at 09:39 AM, 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


More information about the erlang-questions mailing list