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

t x txrev319@REDACTED
Sun Apr 6 06:19:35 CEST 2014


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.


More information about the erlang-questions mailing list