Note: this article is part of explaining compilation outside of IDE.
EurekaLog provides two command-line compilers which performs post-processing: ecc32.exe for Delphi/RAD Studio and emake.exe for C++ Builder. These files are located in the same directory as EurekaLog packages. I.e. like 'C:\Program Files (x86)\Neos Eureka S.r.l\EurekaLog 7\Packages\Studio16\ecc32.exe' (this is just example).
These new compilers integrate the standard dcc32.exe/make.exe features plus the 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. By using the EurekaLog command-line compiler - you can now compile your projects just like when you used the standard compiler, now adding to your projects the new EurekaLog features.
When ecc32.exe/emake.exe/ecc32speed.exe is called - it will compile your project and then add the EurekaLog settings and debug information to the application. Any parameters you pass to ecc32.exe/emake.exe are passed onto dcc32.exe/make.exe as in a normal compilation. The EurekaLog options are taken from the standard project options file.
Note: the emake.exe command-line compiler doesn't support ".bpr"/".bdsproj"/".cbproj" files (it only supports ".mak" files). To generate the ".mak" file from a ".bpr" you can use the bpr2mak.exe command-line program. See also: post-processing without compilation.
So ecc32.exe/emake.exe/ecc32speed.exe can be used just like dcc32.exe/make.exe and you can find plenty of information on these standard parameters in the Delphi help file. There is a minimal standard options which have to be set for EurekaLog to function properly.
Additionally to standard parameters, ecc32.exe/emake.exe/ecc32speed.exe supports custom EurekaLog parameters for customizing post-processing.