24
2.4 Directory Configuration
This section describes how to configure the directory structure of the program when using the TM. When thinking of
the directory structure, it is important to understand the exact meaning of the “working directory” and the form in which
the source files registered to the project are entered “internally” in the system.
Working Directory
When generating a project, the Project Editor asks you to specify a working directory. This working directory has the
following three roles:
z Directory in which to store the project files
z Directory in which to store the objects generated as the result of compilation8
z Directory from which to start the compiler or debugger
When working with a project, this is the directory from which you start the compiler, etc., to which you output objects,
and in which you debug the program. (The source files, etc. do not always need to exist in locations below the working
director.) If you want to store the files output by the compiler in one directory, it may be a good idea to make that
directory the working directory.
Directory for source files, etc.
The directory in which the source files, etc. are registered by the Project Editor is as follows:
z Files located on the same drive as the working directory
These files are registered with a relative path from the working directory
z Files located on a different drive than the working directory
These files are registered with an absolute path
Open the TMK file with an editor to examine how the source files are registered in your system.
8 Prior to TM V2, we had the concept of an output directory. However, because this concept had difficulty processing the source line information and
other problems, we in V3 combined the working directory and output directory into one.