5.5.1 Output Files

The compilation driver can produce output files with the following extensions, which are case-sensitive.

Table 5-3. File Names
Extensions	Definition
`file.hex`	Executable file
`file.elf`	ELF debug file
`file.o`	Object file (intermediate file)
`file.s`	Assembly code file (intermediate file)
`file.i`	Preprocessed C file (intermediate file)
`file.ii`	Preprocessed C++ file (intermediate file)
`file.map`	Map file

The names of many output files use the same base name as the source file from which they were derived. For example the source file input.c will create an object file called input.o.

The main output file is an ELF file called a.elf, unless you override that name using the -o option.

The object files produced by the MPLAB XC32 C/C++ Compiler are compatible with third party tools; however, note that object files built from source code containing Microchip-specific features, such as the address attribute, will not work as expected with these tools unless the linker script and/or startup code has been appropriately customized.

If you are using an IDE, such as MPLAB X IDE, to specify options to the compiler, there is typically a project file that is created for each application. The name of this project is used as the base name for project-wide output files, unless otherwise specified by the user. However check the manual for the IDE you are using for more details.

Note: Throughout this manual, the term project name will refer to the name of the project created in the IDE.

The compiler is able to directly produce a number of the output file formats which are used by Microchip development tools.

The default behavior of xc32-gcc and xc32-g++ is to produce an ELF output. To make changes to the file’s output or the file names, see Driver Option Descriptions.