|
Note: this article is part of explaining compilation outside of IDE.
Important Note: usually, you call ecc32.exe/ecc32speed.exe from [EurekaLog installation folder]\Packages\[IDE name]\ folder. That way ecc32.exe/ecc32speed.exe will know which IDE you are using. However, if you are calling ecc32.exe/ecc32speed.exe from \bin folder of EurekaLog, or if you copy ecc32.exe/ecc32speed.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.
Direct calling of ecc32.exe/ecc32speed.exe rather than using standard EurekaLog expert is often used in automated build scenarios. Many EurekaLog's users setup a build server, where they can build working project automatically without calling IDE. Usually it involves usage some sort of make program (tool) or .bat/.cmd-files. In all those cases compilation is performed by calling dcc32.exe directly. The EurekaLog expert is not used, so it has no chances in adding "EurekaLog's magic" to application.
In those cases you need to manually add a call to ecc32.exe/ecc32speed.exe. There are two options:
See also:
| ||||||||||||