CODEWITHSUNDEEP
erlang
gextra
gextra

Reputation: 8885

How to properly use the deps folder in an Erlang project?

I am coming from the assumption that the deps folder of an erlang project should include symbolic links that point to other projects and applications, so all modules from that project can be accessed/visible.

For example, My project named project_final should access modules from project_a and application_b. The directory structure of them is as follows:

NOTICE: because I am using GIT, the projects have a double structure, so they are not direct siblings to each other, but instead they are placed under /projects/project_X/projectX/etc... I believe this is a problem. Any better suggestions how to manage this ?

/projects/project_a/project_a : contains ( ebin, include, src ) /projects/application_b/application_b : contains ( ebin, include, src )

/project/pro_final:

How I am executing the project_final test module is by:

cd /projects
erl -env ERL_LIBS "."
myprojectfinalmodule:test().
** exception error: undefined function project_a:test/0

The project_a:test module is exported and correct.

Upvotes: 3

Views: 650

Answers (1)

RichardC
RichardC

Reputation: 10557

The deps directory is a Rebar convention, and should probably not be managed in any other way except through Rebar. If you're not using Rebar, don't put dependencies in a subdirectory of the application, put your individual applications under a common lib/ directory instead and use the ERL_LIBS environment variable (see http://erlang.org/doc/man/code.html) to tell Erlang where to look for applications.

Upvotes: 7

Related Questions