This MAKE_APP extension provides functionality to your configuration file to compile, build and deploy Erlang applications and documentation. |
•erlc - This command performs compilation of Erlang source code files (*.erl). Parameters: [...] In this parameter list you can provide one or more of the native Erlang's compiler options, like: ✓{outdir, <directory>} - Case-sensitive string of the output <directory> where the compiled files to be deployed. ✓{i, <directory>} - Case-sensitive string of include compilation directories. ✓return_errors - Reports compilation errors. ✓return_warnings - Reports compilation warnings. ✓warn_export_all - Causes a warning to be emitted if the export_all option has also been given. ✓warn_export_vars - Causes warnings to be emitted for all implicitly exported variables. ✓warn_shadow_vars - Causes warnings to be emitted for "fresh" variables in functional objects. ✓warn_obsolete_guard - Causes warnings to be emitted for calls to old type testing BIFs. ✓warn_deprecated_function - Causes warnings to be emitted for every call to a function known by the compiler as deprecated. ✓warn_unused_function - Causes warnings to be emitted for unused functions. ✓warn_unused_records - Causes warnings to be emitted for unused records. ✓warn_unused_vars - Causes warnings to be emitted for unused variables. ✓warn_unused_import - Causes warnings to be emitted for unused imported functions. ✓{warn_format, <report_level>} - Causes warnings to be emitted for malformed format strings as arguments to io:format functions. ✓compressed - The compiler will compress the generated object code. ✓bin_opt_info - The compiler will emit informational warnings about binary matching optimizations. ✓no_line_info - Omit line number information in order to produce a slightly smaller output file. ✓debug_info - The compiler will Include debug information in the form of abstract code in the compiled beam module. ✓verbose - Causes more verbose information from the compiler. •emake - This command will build and deploy an Erlang release files. It automatically generates the App specification and the release files using the solution's configuration file. Parameters: [...] In this parameter list you can provide one or more of the following parameters: ✓{outdir, <directory>} - Case-sensitive string of the output <directory> where the release files shall be created. ✓warnings_as_errors - Any warning shall be reported as error, therefore the command shall be interrupted. ✓local - Explicitly specifies to generate the boot script locally without relative paths. This is useful for test purposes. •epack - This command creates a release package file of the Erlang solution. Parameters: [...] In this parameter list you can provide one or more of the following parameters: ✓{outdir, <directory>} - Case-sensitive string of the output <directory> where the release package shall be created. ✓{dirs, [<direcotry>, ...]} - List of atoms referring to additional directories that have to be included into the release package. ✓no_warn_sasl - To suppress warnings if SASL is not included as an application. •edoc - This command creates technical documentation of your Erlang's project in accordance with EDoc specification. •eshell - This command prepares a fully-functional Erlang emulator under Windows or Linux and automatically runs your App into emulator's environment. Parameters: [...] In this parameter list you can provide one or more of the following parameters: ✓{config, <config_file>} - Specifies the name of a configuration file of your Erlang App. ✓{name, <erl_node_name>} - Makes the Erlang run-time system into a distributed node with fully qualified host name of the node. ✓{sname, <erl_node_sname>} - Makes the Erlang run-time system into a distributed node with short-name (not fully qualified host name of the node). ✓{setcookie, <erl_cookie>} - Sets the magic cookie of the Erlang's node. ✓command line argument to the Emulator provided as case-sensitive strings, like "+W w +A 100". More information about the Emulator's arguments is published here. |
1)This extension automatically generates the App specification and the release files of your Erlang application using the Solution's specification from your make_app.config file. 2)The extension supports a special option for your projects resource configuration named skip_app. This option allows you to configure and explicitly select which modules should be included into Erlang's App specification. 3)The extension supports also the command line option --all to override the project configuration in case task with erlc command is performed and to rebuild all Erlang source files. This option has no effect on the rest of the exported extension's commands. For example: $ escript make_app.beam my_solution build --all |