[erlang-questions] include as a library rather than an application?

Loïc Hoguin essen@REDACTED
Sun Apr 6 09:09:02 CEST 2014

You don't need the app behaviour to do that.

Loïc Hoguin

-------- Original Message --------
From:t x <txrev319@REDACTED>
Sent:Sun, 06 Apr 2014 06:19:35 +0200
Subject:[erlang-questions] include as a library rather than an application?

>For this problem has a "working hack" -- but I'd prefer to do it without a hack.
>I'm including erldn in my app.src as:
>{applications, [kernel, stdlib, cowboy, gproc, erldn]},
>To do this, erldn must have an application behaviour. Thus, I was forced to add:
>a no-op file to make it an application.
>My question: is there a way to include erldn as a library rather than
>an application? I.e. I want access to erldn:parse_str(...) . However,
>I don't want to spawn an app just to include erldn.
>erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140406/ff706435/attachment.htm>

More information about the erlang-questions mailing list