Chris Kay 8227493637 build: clarify linker script generation ... The following build system variables have been renamed: - `LINKERFILE` -> `DEFAULT_LINKER_SCRIPT` - `BL_LINKERFILE` -> `DEFAULT_LINKER_SCRIPT_SOURCE` - `<IMAGE>_LINKERFILE` -> `<IMAGE>_DEFAULT_LINKER_SCRIPT_SOURCE` These new names better reflect how each variable is used: 1. the default linker script is passed via `-dT` instead of `-T` 2. linker script source files are first preprocessed Additionally, linker scripts are now placed in the build directory relative to where they exist in the source directory. For example, the `bl32/sp_min/sp_min.ld.S` would now preprocess to `sp_min/sp_min.ld` instead of just `bl32.ld` BREAKING-CHANGE: The `LINKERFILE`, `BL_LINKERFILE` and `<IMAGE_LINKERFILE>` build system variables have been renamed. See the commit message for more information. Change-Id: If8cef65dcb8820e8993736702c8741e97a66e6cc Signed-off-by: Chris Kay <chris.kay@arm.com>		2023-02-10 17:01:46 +00:00
..
linker.ld.S	build: clarify linker script generation	2023-02-10 17:01:46 +00:00
trp.mk	build: clarify linker script generation	2023-02-10 17:01:46 +00:00
trp_entry.S	Merge "fix(rmmd): add missing padding to RMM Boot Manifest and initialize it" into integration	2022-12-08 14:53:50 +01:00
trp_helpers.c	feat(rmmd): add support to create a boot manifest	2022-07-04 18:46:34 +01:00
trp_main.c	feat(rme): set DRAM information in Boot Manifest platform data	2023-01-17 16:35:41 +00:00
trp_private.h	fix(rmmd): add missing padding to RMM Boot Manifest and initialize it	2022-12-07 18:54:28 +00:00