Accessing Archived Functions From Your Code - 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

Accessing Archived Functions From Your Code

Programs that call a library routine must use the assembler's
directive to specify the routine's start label as an external label. When link-
ing the program, specify one or more library files (
along with the names of the object files (
searches the library files to resolve symbols and links the appropriate rou-
tines into the executable file.
Any file containing a label referenced by your program is linked into the
executable output file. Linking libraries is faster than using individual
object files, and you do not have to enter all the file names, just the library
name.
In the following example, the archiver creates the
taining the object files:
elfar -c filter.dlb taps.doj coeffs.doj go_input.doj
If you then run the linker with the following command line, the linker
links the object files
example,
ADSP-BF535.ldf
linker -DADSP-BF535 main.doj sum.doj filter.dlb -o main.dxe
Assuming that one or more library routines from
from one or more of the object files, the linker searches the library,
extracts the required routines, and links the routines into the executable.
VisualDSP++ 3.5 Linker and Utilities Manual
for 16-Bit Processors
,
taps.doj
coeffs.doj
and
main.doj
sum.doj
), and creates the executable file (
) to the linker,
.DLB
) to link. The linker then
.DOJ
filter.dlb
, and
go_input.doj.
, uses the default .
filter.dlb
Archiver
.EXTERN
library con-
file (for
LDF
).
main.dxe
are called
6-5

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