| 76d5d32f | 30-Oct-2025 |
Harrison Mutai <harrison.mutai@arm.com> |
fix(build): don't rely on Event Log build tree
Follow proper CMake usage by installing libeventlog and referring to the installed artifacts rather than the build directory. The previous approach rel
fix(build): don't rely on Event Log build tree
Follow proper CMake usage by installing libeventlog and referring to the installed artifacts rather than the build directory. The previous approach relied on build-tree paths, which is considered an anti- pattern and may break across CMake versions since the build layout is not stable or part of the public interface.
This change installs libeventlog into a staging directory and updates the TF-A build to use the installed include and library paths. This improves portability, stability, and compliance with CMake idioms.
Change-Id: I740a558fd6f3163a6af3b122e9e1df558a045872 Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
show more ...
|
| f162e3ab | 29-Sep-2025 |
Chris Kay <chris.kay@arm.com> |
fix(build): forward compiler launcher to CMake
To ensure that compiler launchers like `ccache` are forwarded to CMake, we need to provide them separately via `CMAKE_C_COMPILER_LAUNCHER`.
Change-Id:
fix(build): forward compiler launcher to CMake
To ensure that compiler launchers like `ccache` are forwarded to CMake, we need to provide them separately via `CMAKE_C_COMPILER_LAUNCHER`.
Change-Id: I943d2fb5aaefe3915dbe424cb29277bac6dae799 Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| 3dc41a61 | 25-Sep-2025 |
Chris Kay <chris.kay@arm.com> |
fix(build): force CMake to cross-compile
CMake provides the `CMAKE_SYSTEM_NAME` variable, which identifies the target operating system that the project is being built for. By default this variable i
fix(build): force CMake to cross-compile
CMake provides the `CMAKE_SYSTEM_NAME` variable, which identifies the target operating system that the project is being built for. By default this variable inherits its value from `CMAKE_HOST_SYSTEM_NAME`, which identifies the operating system of the host machine.
If these two variables differ in value, CMake determines that the project is being cross-compiled, and changes some of its behaviours.
For example: on macOS, unless cross-compiling is enabled, CMake passes Apple Clang's `-arch` flag to the C compiler whether it is Apple Clang or not.
To resolve this, this change now sets the following CMake variables:
- `CMAKE_SYSTEM_NAME` to `Generic`, indicating no specific system. - `CMAKE_SYSTEM_VERSION` to ``, to un-inherit the host system version.
See the CMake documentation for the following variables:
- https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_COMPILER.html - https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_HOST_COMPILER.html - https://cmake.org/cmake/help/latest/variable/CMAKE_CROSSCOMPILING.html
Change-Id: Id5406c61baec459f56b6a105b3b507d238ff2847 Signed-off-by: Chris Kay <chris.kay@arm.com>
show more ...
|
| ae8598f5 | 08-Mar-2025 |
Harrison Mutai <harrison.mutai@arm.com> |
refactor(measured-boot): refine event log lib docs
Add comments for all exported functions and move these descriptions to the header file. Moving the descriptions to the header file allows the docum
refactor(measured-boot): refine event log lib docs
Add comments for all exported functions and move these descriptions to the header file. Moving the descriptions to the header file allows the documentation to be easily accessible to any code that includes the header file, without having to look through the source file where the function implementation is located.
Change-Id: I78ad777cb3de1707f9e9df59c721cd6370317c05 Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
show more ...
|
| 8cd09cfc | 17-Jun-2021 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
refactor(measured boot): move BL2 measurement to platform layer
Right now, event_log_init() does 2 things: 1) It writes all the necessary TCG data structures in the event log buffer. 2) It writes th
refactor(measured boot): move BL2 measurement to platform layer
Right now, event_log_init() does 2 things: 1) It writes all the necessary TCG data structures in the event log buffer. 2) It writes the first measurement (BL2's).
Step 2) introduces in the TCG event log driver an assumption on what is getting measured and in what order. Ideally, the driver should only be concerned about generic operations, such as initializing the event log or recording a measurement in it. As much as possible, we should design the driver such that it could be reused in another project that has a different measure boot flow.
For these reasons, move step 2) up to the caller, plat_mboot_init() in this case. Make event_log_record() a public function for this purpose.
This refactoring will also help when we make BL1 record BL2's measurement into the event log (instead of BL2). Both BL1 and BL2 will need to call the driver's init function but only BL1 will need recording BL2's measurement. We can handle this through different implementations of plat_mboot_init() for BL1 and BL2, leaving the TCG event log driver unchanged.
Change-Id: I358e097c1eedb54f82b866548dfc6bcade83d519 Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
show more ...
|
| 9b0b3444 | 17-Jun-2021 |
Sandrine Bailleux <sandrine.bailleux@arm.com> |
refactor(measured boot): rename add_event2()
To a layman in TCG linguo, add_event2() is not straight forward to understand. Rename the function into event_log_record().
Change-Id: I75d53a656425cd78
refactor(measured boot): rename add_event2()
To a layman in TCG linguo, add_event2() is not straight forward to understand. Rename the function into event_log_record().
Change-Id: I75d53a656425cd78a41ebf2c4c4e4e57687adc0d Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
show more ...
|