Note: this article is part of explaining compilation outside of IDE.
Important Note: usually, you call ecc32.exe/emake.exe from [EurekaLog installation folder]\Packages\[IDE name]\ folder or from \bin folder of your IDE. That way ecc32.exe/emake.exe will know which IDE you are using. However, if you are calling ecc32.exe/emake.exe from \bin folder of EurekaLog, or if you copy ecc32.exe/emake.exe to another folder - then it will NOT know which IDE you are using. You have to supply --el_ide command line switch to indicate what IDE should be used.
If you're using build tool (such as IDE, FinalBuilder, etc.) to compile your project, then your project already have all required parameters for EurekaLog. See this article for more information about required parameters and optimal setup.
However, if you're are compiling your project manually - then there is a minimum set of flags needed to get EurekaLog to work. You also need to tell the compiler where EurekaLog files are - so files can be included as part of the compiling process.
Absolute minimum is:
Of course, you have to adjust:
The command line for dcc32.exe would looks like this:
You may need to add more options for your specific case. Please note that minimum options may be not enough for your needs. For example, you may want to have more debug options enabled (such as using debug version of system units, range-checking, etc.). Please see this article for more information about recommended setup.
The command line for ecc32.exe would looks like this:
You may need to add more options for your specific case.
Maybe the simplest way to get a proper command-line for building your project is to install EurekaLog IDE expert (if it's not installed already), allow it to handle your project, compile your project and take a look at actual options for dcc32.exe/make.exe. You can do this via "View" / "Messages" command, switching to "Build" page and expanding dcc command line branch:
A typical command line to build your project without using MS-Build
Note: this feature may be not available in your Delphi version.
If you're using a build script, then you already have this kind of "scary" command line - then all you need to do is to either change dcc32.exe to ecc32.exe, make.exe to emake.exe OR to add additional options as outlined in example above.
If you don't have this "scary" command-line yet - you may want someone else to take care about this. This "someone" can be IDE, build server/tool (like FinalBuilder). And in this case you need to post-process your file without compilation (since compilation along with "scary command-lines" will already be performed by other tool)...