DSC Linker > Input

Use this panel to specify files the DSC Linker should use. You can specify multiple additional libraries and library search paths. Also, you can change the order in which the IDE uses or searches the libraries.

The following table lists and describes the linker input options for DSC.

Table 1. Tools Settings > DSC Linker > Input
Option Description
No Standard Library Uses the system library access paths (specified by %MWLibraries%) and add system libraries (specified by %MWLibraryFiles%) at the end of link order.
Linker Command File Consists of three kinds of segments, which must be in this order:
  • A memory segment, which begins with the MEMORY{} directive.
  • Optional closure segments, which begin with the FORCE_ACTIVE{}, KEEP_SECTION{}, or REF_INCLUDE{} directives.
  • A sections segment, which begins with the SECTIONS{} directive.
Entry Point Specifies the program starting point: the first function the debugger uses upon program start. This default function is in file Finit_MC56F824x_5x_ISR_HW_RESET. It sets up the DSC environment before code execution. Its final task is calling main().
Library Search Paths (-L) Specifies the search pathname of libraries or other resources related to the project. Type the pathname into this text box. Alternatively, click Workspace or File system , then use the subsequent dialog box to browse to the correct location.
Library Recursive Search Paths (-lr) Specifies the recursive user paths that the CodeWarrior IDE searches to find files in your project. You can add several kinds of paths including absolute and project relative.
Additional Libraries Specify multiple additional libraries and library search paths. Also, you can change the order in which the IDE uses or searches the libraries.
Force Active Symbols This option allows you to specify symbols that you do not want the linker to deadstrip. You must specify the symbol(s) you want to keep before you use the SECTIONS keyword.