Compiler Command-Line Interface
If no target is specified with the
ADSP-219x
If the processor identifier is unknown to the compiler, it attempts to read
required switches for code generation from the file
assembler searches for the .
For custom processors, the compiler searches the section "
<processor>.ini
based on an architecture key that is one of the known processors. For
example,
-proc Customxxx
When compiling with the
as well as
__ADSP21XX__
defined as 1. For example,
See also
on silicon revision of the specified processor.
-R directory [{;|,}directory ...]
The
(add source directory) switch directs the compiler to add the spec-
-R
ified directory to the list of directories searched for source files.
On Windows™ platforms, multiple source directories are given as a
comma or semicolon separated list. The compiler searches for the source
files in the order specified on the command line. The compiler searches
the specified directories before reverting to the current project directory.
This option is position-dependent on the command line; that is, it affects
only source files that follow the option.
Source files whose file names begin with
equivalent) and contain drive specifiers (on Windows platforms)
are not affected by this option.
1-42
setting as a default.
file in the VisualDSP ++ System folder.
ini
for key '
architecture
searches the
switch, the appropriate processor macro
-proc
and
__ADSP219X__
__ADSP2191__
"-si-revision version" on page 1-44
VisualDSP++ 3.5 C/C++ Compiler and Library Manual
switch, the system uses the
-proc
<processor>.ini
'. The custom processor must be
file.
Customxxx.ini
preprocessor macros are
and
__ADSP219X__
for more information
,
, or
/
./
../
for ADSP-219x DSPs
. The
" in the
proc
are 1.
(or Windows
Need help?
Do you have a question about the VISUALDSP++ 3.5 and is the answer not in the manual?
Questions and answers