Od Directory; Proc Processor - Analog Devices VisualDSP++ 3.5 Manual

Linker and utilities manual for 16-bit processors
Hide thumbs Also See for VisualDSP++ 3.5:
Table of Contents

Advertisement

-od directory

The
-od directory
$COMMAND_LINE_OUTPUT_DIRECTORY LDF
make a command-line change that propagates to many places without
changing the
.LDF
-pp
The
(end after preprocessing) switch directs the linker to stop after the
-pp
preprocessor runs without linking. The output (preprocessed LDF) prints
to standard output.

-proc processor

The
-proc processor
should produce code suitable for the specified processor.
For example,
linker -proc ADSP-BF535 p0.doj p1.doj p2.doj -o program.dxe
If the processor identifier is unknown to the linker, it attempts to read
required switches for code generation from the file
The linker searches for the .
For custom processors, the linker searches the section "
<processor>.ini
based on an architecture key that is one of the known processors. There-
fore,
-proc Custom-xxx
[proc]
Architecture: ADSP-BF535
See also
on silicon revision of the specified processor.
VisualDSP++ 3.5 Linker and Utilities Manual
for 16-Bit Processors
switch directs the linker to specify the value of the
file. Refer to
"Built-In LDF Macros" on page
(target processor) switch specifies that the linker
file in the VisualDSP ++ System folder.
ini
for key "
architecture
searches the
"-si-revision version" on page 2-46
macro. This switch allows you to
<processor>.ini
". The custom processor must be
file. For example,
Custom-xxx.ini
for more information
Linker
3-21.
.
" in the
proc
2-45

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?

Questions and answers

Related Products for Analog Devices VisualDSP++ 3.5

Table of Contents