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

[Loïc Hoguin]

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

-- 
Loïc Hoguin
http://ninenines.eu

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

>Hi,
>
>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:
>
>https://github.com/txrev319/erldn/blob/d607db5d3826a7f3ad0eff918c8c7691a362ad94/src/erldn_app.erl
>
>
>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.
>
>
>Thanks!
>_______________________________________________
>erlang-questions mailing list
>erlang-questions@REDACTED
>http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140406/ff706435/attachment.htm>