The configuration of the compiler is done through Project à Configuration menu option.
· Preprocessor defines. Write here the –D directives without any options. If you want to #define MYDEF you would write: MYDEF in the edit field. If you have several of those write: MYDEF, MY_OTHER_DEF. This will provoke that the development environment will call the compiler with –DMYDEF and –DMY_OTHER_DEF as command line arguments.
· Include Path. Here you write several paths separated by spaces. It is imperative to put double quotes in path names that have spaces, as shown in the example above. This will be translated by the development environment as: -I"c:\program files\lcc\include". This is just an example. It is NOT necessary to put there the path of the standard includes.
· Generate Asm. This will produce an assembly listing that will have the same name as the source file but an .asm extension.
· Optimize. The compiler will try to generate the best code.
· Generate browse info. Normally the IDE does this automatically, so this is not really necessary.
· Use Pentium pro instructions. If you choose this (command line option –p6) the new p6 instructions will be used and your code will NOT run in a previous processor.
· Structure alignment. This sets the space that the compiler will use to align structures.
· Debugging support level. This can be the strict minimum (Generate debug info) or more sophisticated error reports in case of crash (Run time stack trace support) that can have even line number display.
· Language extensions. Whether to use the lcc-win32 language extensions (operator overloading, etc). Leave this as above.
· Warning level: Self evident.
· Enable profiling. This activates the -profile option of the compiler. See profiler.
· Generate intermediate language file. A .LIL (Lcc Intermediate Language) file is generated. This helps understand how the compiler works.