Caution: this is old EurekaLog 6 documentation. This is not the latest version.

EurekaLog provides two command-line compilers: ecc32.exe for Delphi and emake.exe for C++ Builder. They are located in the same directory as the dcc32.exe/make.exe compilers.

EurekaLog 6.1 and above also contains compiler from EurekaLog 7. It's called el7c.exe (and it's suitable for both Delphi and C++ Builder). It's located in EurekaLog's folder under sub-folder of corresponding IDE version. See EurekaLog 6.1 for more info.

These new compilers integrate the standard dcc32.exe/make.exe features plus the new EurekaLog features, so you can now just use the new ecc32.exe/emake.exe/el7c.exe command-line compiler instead of the standard dcc32.exe/make.exe compiler.

Using the new command-line compiler, you can compile your projects just like when you use the standard compiler, adding to your projects the new EurekaLog features.

If it is used without any EurekaLog custom parameters (see below) it will simply call the standard compiler (dcc32.exe or make.exe) and after that it will alter the compiled file adding the EurekaLog options and debug data. The EurekaLog options are taken from the standard project options file:

The EurekaLog command line compilers have the following additional new options:

--el_config

This is used to compile your project with a different EurekaLog option file. To create a EurekaLog option file you can use the Export button on the EurekaLog options dialog.

--el_alter_exe

This option instructs the EurekaLog compiler to not compile the project and only add the EurekaLog options and debug data into a compiled application (you can also optionally specify the compiled application's filename).

It is useful when used with 3rd party tools that are not able to directly run the ecc32.exe command-line compiler.

Path ".\Debug\Win32\" is only an example. Replace it with your value or just remove it (in case of .exe file being in the same folder as project file).

Part in [] is optional, but recommended.

--el_verbose

This option instructs the EurekaLog compiler to produce more messages for debug purposes. If you have some strange issues with EurekaLog compiler - try to use this option to see what's going wrong.

Usually you don't need this option, it is used only for troubleshooting.

el7c.exe will also create a few debug files. You can safely delete them if they aren't needed. They aren't used by EurekaLog and are generated only for debugging purposes.

--el_path

This option specifies path to EurekaLog's files (dcu or pas). Usually you don't need this option as EurekaLog writes all necessary information into registry, so EurekaLog compiler is able to pick it up. But if you use EurekaLog compiler under the different user account than one, which was used for installation - you need to specify this option with path to EurekaLog's files.

It is useful when used with 3rd party compilation automation tools, like Final Builder or Cruise Control.

See also: KB article.

This option is strongly recommended for el7c.exe compiler, since you don't have EurekaLog 7 installed.

--el_output=el6 (el7c.exe only)

Instructs compiler to produce debug information in EurekaLog 6 format. Mandatory. You must add this switch.

--el_mode (el7c.exe only)

Switches between Delphi and C++ Builder project. Mandatory. You must add this switch. Possible values are "Delphi" or "Builder".

--el_gui_error (el7c.exe only)

Shows errors in message boxes instead of writing them to the console. Optional.

Usually you want to add this, if you run compiler from IDE or other GUI tool. You probably don't want to specify it, if you run compiler from console or automated build script.

--el_target  (el7c.exe only)

Specifies output file name. Optional. By default EurekaLog tries to get this from project's options (which is not always possible). It's not needed for --el_alter_exe switch, since output file name can be specified inside --el_alter_exe switch itself.

Don't use the standard command-line compiler anymore: use only the new EurekaLog command-line compiler.

Note: the emake.exe  command-line compiler does not support ".bpr" files (it only supported ".mak" files). To generate the ".mak" file from a ".bpr" you can use the bpr2mak.exe  command-line program.

See also: Blog article - "Compiling from the Command line".