Similar to object files, executable files are partitioned into output sections
with unique names. Output sections are defined by the Executable and
Linking Format (ELF) file standard to which VisualDSP++ conforms.
The executable's input section names and output section names
occupy different namespaces. Because the namespaces are indepen-
dent, the same section names may be used. The linker uses input
section names as labels to locate corresponding input sections
within object files.
The executable file(s) (.
loaded into the processor or burned onto an EPROM. These files are used
to debug the system.
Directing Linker Operation
Linker operations are directed by these options and commands:
• Linker (
"Linker Command-Line Reference" on page
• Settings (options) on the Link page of the Project Options dialog
box. See
• LDF commands. Refer to
detailed description of the LDF commands.
Linker options control how the linker processes object files and library
files. These options specify various criteria such as search directories, map
file output, and dead code elimination. You select linker options via linker
command-line switches or by settings on the Link page of the Project
Options dialog box within the VisualDSP++ environment.
LDF commands in a Linker Description File (
memory map and the placement of program sections within processor
memory. The text of these commands provides the information needed to
link your code.
VisualDSP++ 3.5 Linker and Utilities Manual
for 16-Bit Processors
) and auxiliary files (
DXE
) command-line switches (options). Refer to
linker.exe
"Project Builds" on page
.SM
2-6.
"LDF Commands" on page 3-23
) define the target
.LDF
Linker
and
) are not
.OVL
2-30.
for a
2-3
Need help?
Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?
Questions and answers