The build tools use several environment variables at build time to search for include files , libraries, and other source files. All of the variables mentioned here are lists which are separated by semicolons (" ;") in Windows operating systems and colons (" :") in Solaris operating systems.
Unless -nodefaults is passed to on the command line, the compiler searches for an environment variable called MWCEABIPPCIncludes or MWCIncludes (in that order). These variables contain a list of system access paths to be searched after the system access paths specified by the user. The assembler also does this, using the variables MWAsmEABIPPCIncludes or MWAsmIncludes.
Analogously, unless -nodefaults or -disassemble is given, the linker will search the environment for a list of system access paths and system library files to be added to the end of the search and link orders. The variable MWEABIPPCLibraries or MWLibraries contains a list of system library paths to search for files, libraries, and command files.
Associated with this list is the variable MWEABIPPCLibraryFiles or MWLibraryFiles which contains a list of libraries (or object files or command files) to add to the end of the link order. These files may be located in any of the cumulative access paths at runtime.
If you are only building for one target, it is okay to use MWCIncludes, MWAsmIncludes, MWLibraries, and MWLibraryFiles. The target-specific versions of the variables come in handy when targeting multiple targets, since the target-specific variables override the generic variables. Note that if the target-specific variable exists, the generic variable will not be used; the contents of the two variables will not be combined.