Help¶

Path to the linker script to be used instead of the one define by the board.

The linker script must be based on a version provided by Zephyr since the kernel can expect a certain layout/certain regions.

This is useful when an application needs to add sections into the linker script and avoid having to change the script provided by Zephyr.

Direct dependencies¶

HAVE_CUSTOM_LINKER_SCRIPT

(Includes any dependencies from ifs and menus.)

Defaults¶

No defaults. Implicitly defaults to the empty string.

Kconfig definition¶

At <Zephyr>/Kconfig.zephyr:140

Included via <Zephyr>/Kconfig:8

Menu path: (Top) → Build and Link Features → Linker Options → Custom linker scripts provided

config CUSTOM_LINKER_SCRIPT
    string "Path to custom linker script"
    depends on HAVE_CUSTOM_LINKER_SCRIPT
    help
      Path to the linker script to be used instead of the one define by the
      board.

      The linker script must be based on a version provided by Zephyr since
      the kernel can expect a certain layout/certain regions.

      This is useful when an application needs to add sections into the
      linker script and avoid having to change the script provided by
      Zephyr.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)