Instructs the compiler to search for include files in the specified directory. When encountering an or directive, the compiler searches for header files in the following directories:

The directory where the compiler should place the output files. If not specified, output files will be placed in the current working directory.

Defines a macro.

Defines a macro with the given value. The value can be any Erlang term. Depending on the platform, the value may need to be quoted if the shell itself interprets certain characters. On Unix, terms which contain tuples and list must be quoted. Terms which contain spaces must be quoted on all platforms.

Makes all warnings into errors.

Sets warning level to number. Default is . Use to turn off warnings.

Same as . Default.

Enables verbose output.

Specifies the type of output file. Generally, output-type is the same as the file extension of the output file but without the period. This option will be ignored by compilers that have a a single output format.

Compile using the SMP emulator. This is mainly useful for compiling native code, which needs to be compiled with the same run-time system that it should be run on.

Produces a Makefile rule to track headers dependencies. The rule is sent to stdout. No object file is produced.

Like the option above, except that the Makefile is written to Makefile. No object file is produced.

Same as .Pbeam]]>.

In conjunction with or , change the name of the rule emitted to Target.

Like the option above, except that characters special to make(1) are quoted.

In conjunction with or , add a phony target for each dependency.

In conjunction with or , consider missing headers as generated files and add them to the dependencies.

Signals that no more options will follow. The rest of the arguments will be treated as file names, even if they start with hyphens.

A flag starting with a plus ('+') rather than a hyphen will be converted to an Erlang term and passed unchanged to the compiler. For instance, the option for the Erlang compiler can be specified as follows:

erlc +export_all file.erl

Depending on the platform, the value may need to be quoted if the shell itself interprets certain characters. On Unix, terms which contain tuples and list must be quoted. Terms which contain spaces must be quoted on all platforms.

Appends directory to the front of the code path in the invoked Erlang emulator. This can be used to invoke another compiler than the default one.

Appends directory to the code path in the invoked Erlang emulator.

Erlang source code. It generates a file.

The options -P, -E, and -S are equivalent to +'P', +'E', and +'S', except that it is not necessary to include the single quotes to protect them from the shell.

Supported options: -I, -o, -D, -v, -W, -b.

Erlang assembler source code. It generates a file.

Supported options: same as for .erl.

Erlang core source code. It generates a file.

Supported options: same as for .erl.

Yecc source code. It generates an file.

Use the -I option with the name of a file to use that file as a customized prologue file (the option).

Supported options: -o, -v, -I, -W (see above).

MIB for SNMP. It generates a file.

Supported options: -I, -o, -W.

A compiled MIB for SNMP. It generates a file.

Supported options: -o, -v.

Script file. It generates a boot file.

Use the -I to name directories to be searched for application files (equivalent to the in the option list for ).

Supported options: -o.

ASN1 file.

Creates an , , and file from an file. Also compiles the using the Erlang compiler unless the options is given.

Supported options: -I, -o, -b, -W.

IC file.

Runs the IDL compiler.

Supported options: -I, -o.