To use the command-line compiler

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.

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 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:

DOF	Delphi 3/7
BDSPROJ	Delphi 2005/2006
DPROJ	Delphi 2007 and later
BPR	C++Builder 5/6
BDSPROJ	C++Builder 2006
CBPROJ	C++Builder 2007 and later

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.

Example

--el_config"Project1.eof"

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.

Delphi Example

--el_alter_exe"ProjectFile.dpr[;ProjectFile.exe]"

C++Builder Example

--el_alter_exe"MakeFile.mak"

--el_alter_exe"ProjectFile.bpr[;ProjectFile.exe]"

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.

Example

--el_verbose

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.

Example

--el_path"C:\Program Files\EurekaLog 6\Delphi11"

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

Delphi command-line compiler

ecc32.exe "ProjectFile.dpr"

C++Builder command-line compiler

emake.exe -B -f"MakeFile.mak"

Note: the emake.exe command-line compiler did 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.