ARM Compiler toolchain Using the Linker - ARM Information Center

9.2 Typical use cases for using ld scripts with armlink
9.2.1 See also
The following are typical use cases for using ld scripts with armlink:
GNU ld script support in armlink
Wrapping libraries
Some libraries have a dynamic and static part. An ld script loads both libraries in
the correct order with the INPUT command, for example:
INPUT(libstatic.a)
INPUT(libdynamic.so)
This script instructs the linker to load libstatic.a then libdynamic.so
Partial linking with the --ldpartial option
An ld script can be given to control how the linker combines sections, for
example:
SECTIONS
{
.text :0
{
*(.text)
*(mysection)
}
}
This script instructs the linker to combine mysection and all the .text sections into
a single .text output section.
Fine control over an ARM linux link
You might want to combine sections together in a different order to that given by
the default linker script. Also, you might want the linker to define symbols at
specific addresses. This information can be given by a custom linker script.
Note
To successfully produce a file that can be run on ARM Linux your image must
include some output sections to contain the meta-data that the dynamic loader can
use to load the file. It is recommended that you start with one of the example
scripts and modify it to suit your purpose.
Concepts
• Example GNU ld script for linking an ARM Linux executable on page 9-12
• Example GNU ld script for linking an ARM Linux shared object on page 9-14
• Example GNU ld script for linking ld --ldpartial object on page 9-16.
Reference
Linker Reference:
• --ldpartial on page 2-94
• --linker_script=ld_script on page 2-100
• --sysroot=path on page 2-169.
ARM DUI 0474C Copyright © 2010-2011 ARM. All rights reserved. 9-3
ID080411 Non-Confidential