Datasheet

Migrating Projects from SDT to ADS
ARM DUI 0064D Copyright © 1999-2001 ARM Limited. All rights reserved. 4-9
• The linker normally finds the correct C or C++ libraries to link with, and it might
use several libraries, so do not specify the C or C++ libraries on the linker
command line.
For example, change:
armlink obj1.o obj2.o armlib_cn.32l -o image.axf
to:
armlink obj1.o obj2.o -o image.axf
Change -info size to -info sizes
In SDT 2.50 and SDT 2.51, the linker accepts either
size or sizes as a qualifier to the
-info option. In ADS, only sizes is accepted.
Change -symbols file to -symbols
In SDT 2.50 and SDT 2.51, the
-symbols option requires a filename as a parameter.
In ADS, the
-symbols option has no parameter. If output to a file is required, use -list
filename
.
Linking old objects
The object file format for ADS is different to that used by SDT.
In SDT, objects are in the ARM proprietary AOF format. In ADS, the format for all
objects and images is the industry standard ELF.
For backwards compatibility, the ADS linker accepts object files in the SDT AOF
format and libraries in the SDT ALF format. However, these formats are obsolete and
will not be supported in future releases.
Note
The byte order of double and long long types has changed.
In SDT, the formats of little-endian
double and big-endian long long are nonstandard.
The ADS compilers and assembler support industry-standard
double and long long
types in both little-endian and big-endian formats. See Byte order of long long and
double on page 2-34 for more information.
If you try to link an ADS object that uses pure-endian double with an SDT object that
uses mixed-endian
double , the linker reports an attribute clash: