| ||||
| Home Products Download Events Support | ||||
Technical Support
On-Line Manuals
LX51 User's Guide
LX51 Introduction 
Linking Programs 
Environment Settings Command Prompt ERRORLEVEL Output Files Code (COD) File Listing (MAP) File Absolute Object File Directives Reference ASSIGN BANKAREA CLASSES CODE DISABLEWARNING IBANKING IXREF MERGEPUBLICS NAME NOAJMP NOAMAKE NOCOMMENTS NODEFAULTLIBRARY NOINDIRECTCALL NOJMPTAB NOLIBSCAN NOLINES NOMAP NOOVERLAY NOPRINT NOPUBLICS NOSORTSIZE NOSYMBOLS NOTYPE OBJECTCONTROLS OVERLAY PAGELENGTH PAGEWIDTH PRINT PRINTCONTROLS PUBLICSONLY PURGE RECURSIONS REGFILE REMOVEUNUSED RESERVE RTX51 RTX51TINY SEGMENTS SEGSIZE SPEEDOVL SPLIT_XDATAGROUP WARNINGLEVEL Locating Program Objects Data Overlaying Code Banking Real-Time Programs Error MessagesOutput Files
The LX51 Linker generates an application-wide source/assembly listing (or code) file, an object module, and a listing (map) file.
- The object file, by default, has no file extension.
- The listing file has the .MAP extension.
If no output filename is specified, the linker uses the filename of the first object file in the input file list for the object module and for the listing file. An error occurs if the first input file contains no extension.
For example:
LX51 PROG1
generates the following fatal error:
*** FATAL ERROR L209: FILE USED IN CONFLICTING CONTEXTS
FILE: PROG1
This error occurs because the name of the input object file is identical to the object file the linker creates. The following example demonstrates how to avoid this problem.
LX51 PROG1 TO PROG1.ABS
This example specifies an output filename (PROG1.ABS) and avoids the prior error.
| Contact Site Map Press Privacy | Copyright © 2012 ARM Ltd and ARM Germany GmbH. All rights reserved. |
