Linker page

Linker Executable:

This is the full path of the linker to call for generating the hex file from assembled object files.

At program startup, PMP searches for an installed MPLAB toolchain and fills in this field automatically with the MPLINK executable. If no MPLAB toolchain is found, a search is made for a GPUTILS toolchain, searching for the GPLINK executable.

Default include path:

This is where the linker will search for included files (typically .lkr files).

PMP also uses this path to find the .lkr files for managing memory allocation. 

The button at right opens a folder choose dialog.

Default library path:

This is where the linker will search for library files (typically .lib files).

(not used by PMP)

The button at right opens a folder choose dialog.

Output path:

This is where the linker will place the generated hex file. 

The button at right opens a folder choose dialog.

The output path is displayed relative to the project's path.

Linker options:

These options are additional options that the linker may need to have, or user options. Default is: empty.

Use debug mode for linker scripts:

If some in circuit debugger have to be used, the linker has to be configured to reserve some memory (code and data) for the debugger usage.

This option will define the DEBUG conditional for the linker.

Other conditional defines values may be needed to complete the configuration, according to the debugger that is used.

This option is not needed to use MPLAB's simulator.

Use the new *_g generic scripts:

This option is for compatibility with old versions of MPLAB that do not have generic scripts.

It has to be always checked for recent versions of MPLAB and GPUTILS.

The linker is GPLINK compatible:

By default this option should be unchecked for MPLINK usage.

If GPLINK is used, this option has to be used since it has a different command line syntax.

Options have to be set accordingly.