| /rk3399_ARM-atf/plat/arm/common/tsp/ |
| H A D | arm_tsp.mk | 03032a95ae953145ee9bd3b2361b6f621a32666a Wed Oct 29 15:27:48 UTC 2025 Chris Kay <chris.kay@arm.com> fix(build): link Event Log library directly
The `libraries` target is a `.PHONY` target to which various real
library targets, including the Event Log library, have been added over
the years. This target is added as a dependency to any target created
with the `MAKE_BL` function. While this might look convenient on the
surface, it also dictates that a library must be linked even to images
it is totally irrelevant for.
The Event Log library is a good example of this; the library is not
typically used by all images, but by attaching itself to the `libraries`
target it becomes mandatory for all of them.
This change returns some of the control over when and where the Event
Log goes to platform maintainers via the introduction of two new
variables:
- `LIBEVLOG_LIBS`: the path to the Event Log static library.
- `LIBEVLOG_INCLUDE_DIRS`: include directories for the public API.
These can be appended to `BLx_LIBS` and `BLx_INCLUDE_DIRS` to include
the Event Log library in the relevant bootloaders.
Change-Id: I3e1a48cd45493334590b34b2ade0c6e29cbfd47a
Signed-off-by: Chris Kay <chris.kay@arm.com>
|
| /rk3399_ARM-atf/drivers/measured_boot/event_log/ |
| H A D | event_log.mk | 03032a95ae953145ee9bd3b2361b6f621a32666a Wed Oct 29 15:27:48 UTC 2025 Chris Kay <chris.kay@arm.com> fix(build): link Event Log library directly
The `libraries` target is a `.PHONY` target to which various real
library targets, including the Event Log library, have been added over
the years. This target is added as a dependency to any target created
with the `MAKE_BL` function. While this might look convenient on the
surface, it also dictates that a library must be linked even to images
it is totally irrelevant for.
The Event Log library is a good example of this; the library is not
typically used by all images, but by attaching itself to the `libraries`
target it becomes mandatory for all of them.
This change returns some of the control over when and where the Event
Log goes to platform maintainers via the introduction of two new
variables:
- `LIBEVLOG_LIBS`: the path to the Event Log static library.
- `LIBEVLOG_INCLUDE_DIRS`: include directories for the public API.
These can be appended to `BLx_LIBS` and `BLx_INCLUDE_DIRS` to include
the Event Log library in the relevant bootloaders.
Change-Id: I3e1a48cd45493334590b34b2ade0c6e29cbfd47a
Signed-off-by: Chris Kay <chris.kay@arm.com>
|
| /rk3399_ARM-atf/plat/rpi/rpi3/ |
| H A D | platform.mk | 03032a95ae953145ee9bd3b2361b6f621a32666a Wed Oct 29 15:27:48 UTC 2025 Chris Kay <chris.kay@arm.com> fix(build): link Event Log library directly
The `libraries` target is a `.PHONY` target to which various real
library targets, including the Event Log library, have been added over
the years. This target is added as a dependency to any target created
with the `MAKE_BL` function. While this might look convenient on the
surface, it also dictates that a library must be linked even to images
it is totally irrelevant for.
The Event Log library is a good example of this; the library is not
typically used by all images, but by attaching itself to the `libraries`
target it becomes mandatory for all of them.
This change returns some of the control over when and where the Event
Log goes to platform maintainers via the introduction of two new
variables:
- `LIBEVLOG_LIBS`: the path to the Event Log static library.
- `LIBEVLOG_INCLUDE_DIRS`: include directories for the public API.
These can be appended to `BLx_LIBS` and `BLx_INCLUDE_DIRS` to include
the Event Log library in the relevant bootloaders.
Change-Id: I3e1a48cd45493334590b34b2ade0c6e29cbfd47a
Signed-off-by: Chris Kay <chris.kay@arm.com>
|
| /rk3399_ARM-atf/plat/imx/imx8m/imx8mm/ |
| H A D | platform.mk | 03032a95ae953145ee9bd3b2361b6f621a32666a Wed Oct 29 15:27:48 UTC 2025 Chris Kay <chris.kay@arm.com> fix(build): link Event Log library directly
The `libraries` target is a `.PHONY` target to which various real
library targets, including the Event Log library, have been added over
the years. This target is added as a dependency to any target created
with the `MAKE_BL` function. While this might look convenient on the
surface, it also dictates that a library must be linked even to images
it is totally irrelevant for.
The Event Log library is a good example of this; the library is not
typically used by all images, but by attaching itself to the `libraries`
target it becomes mandatory for all of them.
This change returns some of the control over when and where the Event
Log goes to platform maintainers via the introduction of two new
variables:
- `LIBEVLOG_LIBS`: the path to the Event Log static library.
- `LIBEVLOG_INCLUDE_DIRS`: include directories for the public API.
These can be appended to `BLx_LIBS` and `BLx_INCLUDE_DIRS` to include
the Event Log library in the relevant bootloaders.
Change-Id: I3e1a48cd45493334590b34b2ade0c6e29cbfd47a
Signed-off-by: Chris Kay <chris.kay@arm.com>
|
| /rk3399_ARM-atf/plat/qemu/qemu/ |
| H A D | platform.mk | 03032a95ae953145ee9bd3b2361b6f621a32666a Wed Oct 29 15:27:48 UTC 2025 Chris Kay <chris.kay@arm.com> fix(build): link Event Log library directly
The `libraries` target is a `.PHONY` target to which various real
library targets, including the Event Log library, have been added over
the years. This target is added as a dependency to any target created
with the `MAKE_BL` function. While this might look convenient on the
surface, it also dictates that a library must be linked even to images
it is totally irrelevant for.
The Event Log library is a good example of this; the library is not
typically used by all images, but by attaching itself to the `libraries`
target it becomes mandatory for all of them.
This change returns some of the control over when and where the Event
Log goes to platform maintainers via the introduction of two new
variables:
- `LIBEVLOG_LIBS`: the path to the Event Log static library.
- `LIBEVLOG_INCLUDE_DIRS`: include directories for the public API.
These can be appended to `BLx_LIBS` and `BLx_INCLUDE_DIRS` to include
the Event Log library in the relevant bootloaders.
Change-Id: I3e1a48cd45493334590b34b2ade0c6e29cbfd47a
Signed-off-by: Chris Kay <chris.kay@arm.com>
|
| /rk3399_ARM-atf/plat/arm/common/ |
| H A D | arm_common.mk | 03032a95ae953145ee9bd3b2361b6f621a32666a Wed Oct 29 15:27:48 UTC 2025 Chris Kay <chris.kay@arm.com> fix(build): link Event Log library directly
The `libraries` target is a `.PHONY` target to which various real
library targets, including the Event Log library, have been added over
the years. This target is added as a dependency to any target created
with the `MAKE_BL` function. While this might look convenient on the
surface, it also dictates that a library must be linked even to images
it is totally irrelevant for.
The Event Log library is a good example of this; the library is not
typically used by all images, but by attaching itself to the `libraries`
target it becomes mandatory for all of them.
This change returns some of the control over when and where the Event
Log goes to platform maintainers via the introduction of two new
variables:
- `LIBEVLOG_LIBS`: the path to the Event Log static library.
- `LIBEVLOG_INCLUDE_DIRS`: include directories for the public API.
These can be appended to `BLx_LIBS` and `BLx_INCLUDE_DIRS` to include
the Event Log library in the relevant bootloaders.
Change-Id: I3e1a48cd45493334590b34b2ade0c6e29cbfd47a
Signed-off-by: Chris Kay <chris.kay@arm.com>
|