|
|||
| Products Download Events Support Videos | |||
Technical Support
On-Line Manuals
Linker User Guide
Conventions and feedback
Overview of the linker
Linking models supported by armlink
Image structure and generation
The image structure
Input sections, output sections, regions, and Prog
Load view and execution view of an image
Methods of specifying an image memory map with the
Types of simple image
Type 1 image, one load region and contiguous execu
Type 2 image, one load region and non-contiguous e
Type 3 image, two load regions and non-contiguous
Image entry points
About specifying an initial entry point
Section placement with the linker
Placing sections with FIRST and LAST attributes
Section alignment with the linker
Demand paging
About ordering execution regions containing Thumb
Overview of veneers
Veneer sharing
Veneer types
Generation of position independent to absolute ven
Reuse of veneers when scatter-loading
Using command-line options to control the generati
About weak references and definitions
How the linker performs library searching, selecti
Controlling how the linker searches for the ARM st
Specifying user libraries when linking
How the linker resolves references
Use of the strict family of options in the linker
Using linker optimizations
Getting information about images
Accessing and managing symbols with armlink
Using scatter files
Linker User Guide
How the linker performs library searching, selection, and scanning
| |||
| Home > Image structure and generation > How the linker performs library searching, selection, and scanning | |||
The linker always searches user libraries before the ARM libraries.
If you specify the --no_scanlib command-line option,
the linker does not search for the default ARM libraries and uses
only those libraries that are specified in the input file list to
resolve references.
The linker creates an internal list of libraries as follows:
Any libraries explicitly specified in the input file list are added to the list.
The user-specified search path is examined to identify ARM standard libraries to satisfy requests embedded in the input objects.
The best-suited library variants are chosen from the searched directories and their subdirectories. Libraries supplied by ARM have multiple variants that are named according to the attributes of their members.
Be aware of the following differences between the way the linker adds object files to the image and the way it adds libraries to the image:
Each object file in the input list is added to the output image unconditionally, whether or not anything refers to it. At least one object must be specified.
A member from a library is included in the output only if:
an object file or an already-included library member makes a non-weak reference to it
the linker is explicitly instructed to add it.
Note
If a library member is explicitly requested in the input file list, the member is loaded even if it does not resolve any current references. In this case, an explicitly requested member is treated as if it is an ordinary object.
Unresolved references to weak symbols do not cause library members to be loaded.
See also| Copyright © 2007-2008, 2011-2012 ARM. All rights reserved. | ARM DUI 0377D |
| Non-Confidential | ID062912 |
 PDF version | |
| Home > Image structure and generation > How the linker performs library searching, selection, and scanning |
ProductsDevelopment Tools |
Hardware & Collateral |
Downloads |
Support |
Buy |
|
 |
|||
