Changes in Makefile

69520877af7b3f6560d3781e2408a86c13434e8b - Merge changes from topic "bk/multibuild" into integration

Mon, 07 Jul 2025 16:55:23 +0000

Merge changes from topic "bk/multibuild" into integration* changes: fix(lx2160a): put cert_create_tbbr.mk in the standard location feat(build): put crttool in the build directory feat(build): put enctool in the build directory feat(build): put fiptool in the build directory build(marvell): avoid using recursive expansion for BLE_INCLUDES List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

f4595e6e4f3659ee6deec9490a243a1b84333f85 - feat(build): put crttool in the build directory

Tue, 06 May 2025 16:11:29 +0000

feat(build): put crttool in the build directorySame as fiptool. Move all artefacts to the platform build directory andconvert to the standard build macro to make things more generic. Leavea symlink for the final binary in case someone depends on it.Change-Id: I82ef846a95474ba385377032fb185e548827bf5cSigned-off-by: Boyan Karatotev List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

d6dccfb01af512fb494b1e3c7ff23ef841738f3b - Merge "build: remove Windows compatibility layer" into integration

Mon, 20 Jan 2025 11:52:16 +0000

Merge "build: remove Windows compatibility layer" into integration List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

c32737033cf2b0ae9649a08273c07b739d368818 - build: remove Windows compatibility layer

Mon, 13 Jan 2025 15:57:32 +0000

build: remove Windows compatibility layerFor a couple of releases now we have officially withdrawn support forbuilding TF-A on Windows using the native environment, relying insteadon POSIX emulation layers like MSYS2, Mingw64, Cygwin or WSL.This change removes the remainder of the OS compatibility layerentirely, and migrates the build system over to explicitly relying on aPOSIX environment.Change-Id: I8fb60d998162422e958009afd17eab826e3bc39bSigned-off-by: Chris Kay List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

1297a45d6ad8ff49b875fc60645d9c46ed099514 - Merge changes from topic "dynamic-toolchain" into integration

Wed, 25 Sep 2024 11:53:54 +0000

Merge changes from topic "dynamic-toolchain" into integration* changes: build: allow multiple toolchain defaults build: determine toolchain tools dynamically List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

3789c3c0009028bd7730c6cead64ef3f7d071bd6 - build: determine toolchain tools dynamically

Mon, 03 Jun 2024 11:10:11 +0000

build: determine toolchain tools dynamicallySince the introduction of the toolchain detection framework into thebuild system, we have done determination and identification of thetoolchain(s) used for the build at the initialization of the buildsystem.This incurs a large cost to the build every time - for every toolchainthat has been requested by the current makefile, we try to identify eachtool in the list of known tool classes, even if that tool doesn'tactually see any use.For the clean and check-like targets we worked around this by disablingmost of the toolchains if we detect these targets, but this isinflexible and not very reliable, and it still means that when buildingnormal targets we are incurring that cost for all tools whether they areused or not.This change instead modifies the toolchain detection framework to onlyinitialize a tool for a given toolchain when it is first used. This doesmean that we can no longer warn about an incorrectly-configuredtoolchain at the beginning of build system invocation, but it has theadvantage of substantially reducing build time and the complexity of*using* the framework (at the cost of an increase in complexity in theframework itself).Change-Id: I7f3d06b2eb58c1b26a846791a13b0037f32c8013Signed-off-by: Chris Kay List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

6d01ea40c9ad509428f7a44fec796b25c2668938 - Merge changes Ida537d4c,Ieda75bba into integration

Tue, 02 Jul 2024 14:09:48 +0000

Merge changes Ida537d4c,Ieda75bba into integration* changes: build(encrypt-fw): don't generate `build_msg.c` build(cert-create): don't generate `build_msg.c` List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

a004ee8de72e622b5b6ef35f163d168e05810a65 - build(cert-create): don't generate `build_msg.c`

Fri, 14 Jun 2024 11:31:03 +0000

build(cert-create): don't generate `build_msg.c`This change avoids generating a build message source file on the shell,instead using the `__DATE__` and `__TIME__` macros directly.Change-Id: Ieda75bbac174847c716701bce8dd10b8e9975902Signed-off-by: Chris Kay List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

cd8eb18d580e9c413ec9e2c33ebf32992ffd31ca - Merge changes from topic "ck/tf-a/verbosity-cleanup" into integration

Mon, 17 Jun 2024 09:01:49 +0000

Merge changes from topic "ck/tf-a/verbosity-cleanup" into integration* changes: build: unify verbosity handling build: add facilities for interpreting boolean values build: add string casing facilities to utilities List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

7c4e1eea61a32291a6640070418e07ab98b42442 - build: unify verbosity handling

Thu, 02 May 2024 17:52:37 +0000

build: unify verbosity handlingThis change introduces a few helper variables for dealing with verboseand silent build modes: `silent`, `verbose`, `q` and `s`.The `silent` and `verbose` variables are boolean values determiningwhether the build system has been configured to run silently orverbosely respectively (i.e. with `--silent` or `V=1`).These two modes cannot be used together - if `silent` is truthy then`verbose` is always falsy. As such: make --silent V=1... results in a silent build.In addition to these boolean variables, we also introduce two newvariables - `s` and `q` - for use in rule recipes to conditionallysuppress the output of commands.When building silently, `s` expands to a value which disables thecommand that follows, and `q` expands to a value which supppressesechoing of the command: $(s)echo 'This command is neither echoed nor executed' $(q)echo 'This command is executed but not echoed'When building verbosely, `s` expands to a value which disables thecommand that follows, and `q` expands to nothing: $(s)echo 'This command is neither echoed nor executed' $(q)echo 'This command is executed and echoed'In all other cases, both `s` and `q` expand to a value which suppressesechoing of the command that follows: $(s)echo 'This command is executed but not echoed' $(q)echo 'This command is executed but not echoed'The `s` variable is predominantly useful for `echo` commands, where youalways want to suppress echoing of the command itself, whilst `q` ismore useful for all other commands.Change-Id: I8d8ff6ed714d3cb401946c52955887ed7dca602bSigned-off-by: Chris Kay List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

60dd8069bfa4e65e3320d4ec8f0b6c981f8abaef - Merge "build: use new toolchain variables for tools" into integration

Tue, 20 Feb 2024 15:06:35 +0000

Merge "build: use new toolchain variables for tools" into integration List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

084c9d3c0de8ed9eb1afd7057c5a2a41c11d9443 - Merge "build: refactor toolchain detection" into integration

Tue, 20 Feb 2024 15:04:53 +0000

Merge "build: refactor toolchain detection" into integration List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

ffb7742125def3e0acca4c7e4d3215af5ce25a31 - build: use new toolchain variables for tools

Mon, 04 Dec 2023 12:03:51 +0000

build: use new toolchain variables for toolsThis change migrates the values of `CC`, `CPP`, `AS` and other toolchainvariables to the new `$(toolchain)-$(tool)` variables, which wereintroduced by the toolchain refactor patch. These variables should beequivalent to the values that they're replacing.Change-Id: I644fe4ce82ef1894bed129ddb4b6ab94fb04985dSigned-off-by: Chris Kay List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

cc277de81692cf72f067354ada6e84f5e996f6b8 - build: refactor toolchain detection

Fri, 20 Oct 2023 09:17:33 +0000

build: refactor toolchain detectionThis change refactors how we identify the toolchain, with the ultimateaim of eventually cleaning up the various mechanisms that we employ toconfigure default tools, identify the tools in use, and configuretoolchain flags.To do this, we introduce three new concepts in this change:- Toolchain identifiers,- Tool class identifiers, and- Tool identifiers.Toolchain identifiers identify a configurable chain of tools targetingone platform/machine/architecture. Today, these are:- The host machine, which receives the `host` identifier,- The AArch32 architecture, which receives the `aarch32` identifier, and- The AArch64 architecture, which receivs the `aarch64` identifier.The tools in a toolchain may come from different vendors, and are notnecessarily expected to come from one single toolchain distribution. Inmost cases it is perfectly valid to mix tools from different toolchaindistributions, with some exceptions (notably, link-time optimizationgenerally requires the compiler and the linker to be aligned).Tool class identifiers identify a class (or "role") of a tool. Ccompilers, assemblers and linkers are all examples of tool classes.Tool identifiers identify a specific tool recognized and supported bythe build system. Every tool that can make up a part of a toolchain mustreceive a tool identifier.These new identifiers can be used to retrieve information about thetoolchain in a more standardized fashion.For example, logic in a Makefile that should only execute when the Ccompiler is GNU GCC can now check the tool identifier for the C compilerin the relevant toolchain: ifeq ($($(ARCH)-cc-id),gnu-gcc) ... endifChange-Id: Icc23e43aaa32f4fd01d8187c5202f5012a634e7cSigned-off-by: Chris Kay List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

0e04a201706346cc87a3659d4502e69751a0b3da - Merge "build(tools): avoid unnecessary link" into integration

Wed, 05 Jul 2023 12:50:04 +0000

Merge "build(tools): avoid unnecessary link" into integration List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

aa57ce632c629fe72ff417e261e0f5bfd8db6bab - build(tools): avoid unnecessary link

Tue, 04 Jul 2023 14:14:02 +0000

build(tools): avoid unnecessary linkIn their respective makefiles, cert_create, encrypt_fw and fiptooldepend on the --openssl phony target as a prerequisite. This forcesthose tools to be re-linked each time.Move the dependencies on the --openssl target from the tools to theirmakefiles all targets, to avoid unnecessary linking while preserving theOpenSSL version printing done in the --openssl targets when in debug.Fixes: cf2dd17ddda2 ("refactor(security): add OpenSSL 1.x compatibility")Signed-off-by: Vincent Stehlé Change-Id: I98a3ab30f36dffc253cecaaf3a57d2712522135d List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

797d7446a0863b8633537f5d386e87287d7f25aa - Merge "refactor(security): add OpenSSL 1.x compatibility" into integration

Fri, 11 Nov 2022 18:59:58 +0000

Merge "refactor(security): add OpenSSL 1.x compatibility" into integration List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

cf2dd17ddda2f44f5dedddcaf48300d16358597a - refactor(security): add OpenSSL 1.x compatibility

Tue, 25 Oct 2022 23:41:02 +0000

refactor(security): add OpenSSL 1.x compatibilityWhen updated to work with OpenSSL 3.0, the host tools lost theircompatibility with previous versions (1.x) of OpenSSL. This ismainly due to the fact that 1.x APIs became deprecated in 3.0 andtherefore their use cause compiling errors. In addition, updatingfor a newer version of OpenSSL meant improving the stabilityagainst security threats. However, although version 1.1.1 isnow deprecated, it still receives security updates, so it wouldnot imply major security issues to keep compatibility with it too.This patch adds backwards compatibility with OpenSSL 1.x versionsby adding back 1.x API code. It defines a macro USING_OPENSSL3,which will select the appropriate OpenSSL API version depending onthe OpenSSL library path chosen (which is determined by thealready-existing OPENSSL_DIR variable).In addition, cleanup items were packed in functions and moved tothe proper modules in order to make the code more maintainable andlegible.Signed-off-by: Juan Pablo Conde Change-Id: I8deceb5e419edc73277792861882404790ccd33c List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

f3249498217d88f3c1a6938d712dec256ce88c52 - Merge changes from topic "lw/cca_cot" into integration

Fri, 24 Jun 2022 10:44:06 +0000

Merge changes from topic "lw/cca_cot" into integration* changes: feat(arm): retrieve the right ROTPK for cca feat(arm): add support for cca CoT feat(arm): provide some swd rotpk files build(tbbr): drive cert_create changes for cca CoT refactor(arm): add cca CoT certificates to fconf feat(fiptool): add cca, core_swd, plat cert in FIP feat(cert_create): define the cca chain of trust feat(cca): introduce new "cca" chain of trust build(changelog): add new scope for CCA refactor(fvp): increase bl2 size when bl31 in DRAM List of files: /rk3399_ARM-atf/tools/cert_create/Makefile

0a6bf811d7f873a180ef4b9f96f5596b26d270c6 - feat(cert_create): define the cca chain of trust

Thu, 21 Apr 2022 21:21:53 +0000

feat(cert_create): define the cca chain of trustSelection of the cca chain of trust is done through the COT buildoption:> make COT=ccaSigned-off-by: Lauren Wehrmeister Change-Id: I123c0a841f67434633a3123cc1fa3e2318585482 List of files: /rk3399_ARM-atf/tools/cert_create/Makefile