The .EXT section is an EXECUTIVE section - a section that does something and works with single files. Commands typed here are executed if you have a source file open and you click the COMPILE button.
This is not a section with the name .EXT but rather a section with the extension of your source file(s), e.g. ".C". In one config file there can be none, one or multiple sections like this. It depends on the number of types of source files that your compiler can use.
Format of the keys used here is the same as in the Build section with a few additions and one difference. The difference is that in the Out key you may not set $T, but for example $In.obj, where $In represents the name of a source file. In Cmd0~CmdN you can then use $O, where $O will be "somefile.obj".
Some of compilers like C & Asm use INCLUDE files to store declarations of functions and variables. If this include file is modified the source file must be recompiled so you must tell UEStudio how to search for include files in sources. There are some keys that can help you to set this:
|
Keys |
Usage |
|
IncFiles = 0/1 |
if set to "1", UEStudio will search for included files in your source file |
|
CaseSensitive = 0/1 |
indicates if keywords in your source file are case sensitive (1) or not |
|
IncDirs = .;$(INCLUDE); |
Most compilers store system include files in special directories like INCLUDE, or INC so you must tell UEStudio where it must search for these files. I recommended you to set as the first path "." as this provides that the directory where your source file is will be searched first |
|
IncKeyWords=#include; |
one or more keywords that are used by the preprocessor of your compiler to include files may be listed here |
|
Comments = /*.*/.//.eol. |
multi-line comment brackets and single line comment brackets are set here Most compilers support comments. The part of your source code that is enclosed by comments is not compiled so it must not be searched for include files. Comment brackets MUST be in pairs. Single line comments must appear as: ";.eol." or "//.eol." where ".eol." stands for "to the end-of-line". Comment brackets are delimited with points ".". Do NOT put spaces between comment brackets and "." ! |
If your compiler can work with more than one type of file with the same options, do not create a section for all these extensions. Instead create only one section, e.g. [.C] and in the [General] section add keys like this: .CPP=.C or .ASM=.C and so on.