I have an Emakefile that looks like:
%% --
%%
%% --
{'/Users/user/projects/custom_test/trunk/*',
[debug_info,
{outdir, "/Users/user/projects/custom_test/trunk/ebin"},
{i, "/Users/user/projects/custom_test/trunk/include/."}
]
}.
Erlang programs must be compiled to object code. The compiler can generate a new file that contains the object code. The current abstract machine, which runs the object code, is called BEAM, therefore the object files get the suffix . beam.
To print a complete list of the options to produce list files, type compile:options() at the Erlang shell prompt. The options are printed in the order that the passes are executed.
1/ {"source files globbed", Options}
Here the options are :
debug_info
add debug info for the debugger
{outdir, "/Users/user/projects/custom_test/trunk/ebin"}
where should the output be written (the .beam files)
{i, "/Users/user/projects/custom_test/trunk/include/."}
where to find the .hrl
header files.
2/ erl -make
3/ erl -pa /Users/user/projects/custom_test/trunk/ebin
starts a shell.
Find the module serving as an entry point in your application and call the functions :
module:start().
You can also run the code non interactively :
erl -noinput -noshell -pa /Users/user/projects/custom_test/trunk/ebin -s module start
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With