title: How to properly use the deps folder in an Erlang project?
body: <p>I am coming from the assumption that the <strong>deps</strong> folder of an erlang project should include <strong>symbolic links</strong> that point to other projects and applications, so all modules from that project can be accessed/visible. </p>
  
  <p>For example, My project named <strong>project_final</strong> should access modules from <strong>project_a</strong> and <strong>application_b</strong>. The directory structure of them is as follows:</p>
  
  <p>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 ? </p>
  
  <p>/projects/project_a/project_a : contains ( ebin, include, src )
  /projects/application_b/application_b : contains ( ebin, include, src )</p>
  
  <p>/project/pro_final:</p>
  
  <ul>
  <li><strong>deps</strong> : has <strong>symbolic links</strong> that point to project_a and application_b</li>
  <li>ebin</li>
  <li>include</li>
  <li>src : contain modules that use project_a and applicabion_b module's functions, <strong>but gives exception error: undefined function</strong>.</li>
  </ul>
  
  <p>How I am executing the <strong>project_final</strong> test module is by:</p>
  
  <pre><code>cd /projects
  erl -env ERL_LIBS "."
  myprojectfinalmodule:test().
  ** exception error: undefined function project_a:test/0
  </code></pre>
  
  <p>The project_a:test module is exported and correct. </p>