User`s guide

Projects and Workspaces
© 2006 Microchip Technology Inc. DS51519B-page 65
4.5 PROJECT FOLDERS AND FILES
Depending on how you have structured your project (see Section 4.4 “Setting Up a
Project Structure – Relative Paths”) and how you have defined the project paths
(Project>Build Options>Project
, General tab), your project files may be all in the main
project folder or spread out into separate subfolders. The structure represented in the
Project window tree, however, will be based on which files you have specifically added
to the project and the file type. The Project window “virtual” folders only contain files of
a type specified by that folder’s filter. To add files, either (1) right click on the main
project folder, select “Add Files” and the file will be placed in the correct subfolder
based on its type or (2) right click on one of the subfolders and select “Add Files” if you
already know the type.
TABLE 4-1: PROJECT FILE TYPES
File Type Example Files Description
Source Files* file.asm
file.c, file.s
These are the only files that the toolsuite will accept
as input to its file commands.
Header Files* header.inc
header.h
MPLAB
®
IDE does not use this category when build-
ing. Consider it a means to document a project's
dependency on a header file, and a convenient
method to access these files. You can double click
on a file in the Project window to open the file in an
editor.
Object Files* ofile.o This category is for precompiled object files, not
object files that result from assembling or compiling
the project's source files. Functionally, the files in this
category are indistinct from the library files, because
both are merely linked in at the final phase of the
build.
Library Files* fft.o
Libfft.a
The toolsuite should take all of the files in this folder,
as well as the object files, and include them in the
final link step.
Linker Scripts* linker.lkr
linker.gld
There should be only one file in this folder. If the user
has more than one linker script, only the first one has
any effect. This is the linker script that the tool will
use in the link step.
Intermediary Files The project maintains this folder, but does not display
it to the user. As source files are assembled and
compiled, links are created to the resulting object
files in this folder. Each and every object file in this
folder should be included in the link step, in addition
to the contents of the Object Files and Library Files
folder.
Note: These files will be destroyed when the user
executes the Clean command.
Output Files project.coff
project.map
This folder is maintained by the project but not dis-
played. These are the final output files that result
from the link step.
Note: A Clean will delete all of these files.