Setting the Search Paths for Erlang Loading Code

   The Erlang runtime system makes use of a code autoloading mechanism. For this to work correctly, you must set a number of search paths in order to find the correct version of your code.

 

  When the system tries to call a function in a module that has not been loaded, an exception occurs, and the system tries to find an object code file for the missing module. If the missing module is called myMissingModule, then the code loader will search for a file called myMissingModule.beam in all the directories that are in the current load path. The
search stops at the first matching file, and the object code in this file is loaded into the system.

 

code:get_path().
[".",
"/usr/local/lib/erlang/lib/kernel-2.11.3/ebin",
"/usr/local/lib/erlang/lib/stdlib-1.14.3/ebin",
"/usr/local/lib/erlang/lib/xmerl-1.1/ebin",
"/usr/local/lib/erlang/lib/webtool-0.8.3/ebin",
"/usr/local/lib/erlang/lib/typer-0.1.0/ebin",
"/usr/local/lib/erlang/lib/tv-2.1.3/ebin",
"/usr/local/lib/erlang/lib/tools-2.5.3/ebin",
"/usr/local/lib/erlang/lib/toolbar-1.3/ebin",
"/usr/local/lib/erlang/lib/syntax_tools-1.5.2/ebin",
...]

 

• @spec code:add_patha(Dir) => true | {error, bad_directory}
  Add a new directory, Dir, to the start of the load path.
• @spec code:add_pathz(Dir) => true | {error, bad_directory}
  Add a new directory, Dir, to the end of the load path.

Alernatively, there is the command line.

 

> erl -pa Dir1 -pa Dir2 ... -pz DirK1 -pz DirK2