The linker supports relative and absolute directory names, default directo-
ries, and user-selected directories for file search paths. File searches occur
in the following order.
1. Specified path – If the command line includes relative or absolute
path information on the command line, the linker searches that
location for the file.
2. Specified directories – If you do not include path information
on the command line and the file is not in the default directory,
the linker searches for the file in the search directories specified
with the
tories specified by
Directories are searched in order of appearance on the command
line or in the .
3. Default directory – If you do not include path information in the
file named by the
.LDF
file in the current working directory. If you use a default
(by omitting LDF information in the command line and instead
specifying
sor-specific
For more information on file searches, see
page
3-21.
When providing input or output file names as command-line parameters:
• Use a space to delimit file names in a list of input files.
• Enclose file names that contain spaces within straight quotes; for
example, "
• Include the appropriate extension to each file. The linker opens
existing files and verifies their type before processing. When the
linker creates a file, it uses the file extension to determine the type
of file to create.
VisualDSP++ 3.5 Linker and Utilities Manual
for 16-Bit Processors
(path) command-line switch, and then searches direc-
-L
SEARCH_DIR
file.
LDF
switch, the linker searches for the
-T
-proc <processor>
directory; for example, ...
LDF
".
long file name
commands in the
), the linker searches in the proces-
\$ADI_DSP\Blackfin\ldf
"Built-In LDF Macros" on
Linker
file.
.LDF
.LDF
file
.LDF
.
2-33
Need help?
Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?