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/fiptool/Makefile

cbd6cec3c35f22733034fbdd4801efe20d26ba9a - feat(build): put fiptool in the build directory

Fri, 02 May 2025 14:08:24 +0000

feat(build): put fiptool in the build directoryFor some reason, tools are not built in the build directory, but ratherin the source directory, regardless of what BUILD_BASE might say. Thisis especially annoying when trying to have a few builds going at thesame time (like in a CI). For example, run A may check if a file Xexists. Seeing that it does not, it will start building the file. At thesame time, run B may also check if file X exists but before A haswritten it, starting a build again. Then it is possible for A to use thefile it believes to have built right at the moment B begins writing toit (and truncating it beforehand). This results in gcc failing to read afail and a failed build. The more parallel runs there are, the morelikely this is to happen, and this is virtually guaranteed to happenwith just a handful onwards.So move fiptool and all of its build artefacts to the build directory.Since there are platform differences between the various fiptoolincarnations, this goes in the plat build rather than a more top-levellocation.This patch adds the build macro MAKE_TOOL to do this generically for anykind of tool since the other tools suffer from the same shortfall. Thismacro takes care to use unique names for every type of argument thatbuilding a tool might need. The fiptool makefile and platform add-onsare updated accordingly.This should have never been allowed in the first place, but downstreamscripts almost certainly depend on this behaviour now. So add a symlinkin the place of the old fiptool so these continue working. With anyluck, this will be removed in the future.Change-Id: I3d4d87dab0f53deab5b43fbc6652146f0e4e7e81Signed-off-by: Boyan Karatotev List of files: /rk3399_ARM-atf/tools/fiptool/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/fiptool/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/fiptool/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/fiptool/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/fiptool/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/fiptool/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/fiptool/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/fiptool/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/fiptool/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/fiptool/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/fiptool/Makefile

7c3ff62d22270e945d04e3bbf761790c9955a293 - Merge "feat(fiptool): add ability to build statically" into integration

Tue, 26 Sep 2023 15:46:18 +0000

Merge "feat(fiptool): add ability to build statically" into integration List of files: /rk3399_ARM-atf/tools/fiptool/Makefile

4d4fec281861066ab2249bc3db7c2decdd176f34 - feat(fiptool): add ability to build statically

Thu, 31 Aug 2023 09:46:54 +0000

feat(fiptool): add ability to build staticallyProvide a STATIC command line build option for platforms willing tobuild fiptool statically and remove dependency to toolchain and OpenSSLlibraries.Signed-off-by: Olivier Deprez Change-Id: I1d1b6676df50081828170e2b0ab7b71c4ec19d6e List of files: /rk3399_ARM-atf/tools/fiptool/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/fiptool/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/fiptool/Makefile

c89fdb4a51cae5a353f81bb734f57e2e617596b2 - Merge "refactor(fiptool): move plat_fiptool.mk to tools" into integration

Tue, 02 May 2023 08:47:15 +0000

Merge "refactor(fiptool): move plat_fiptool.mk to tools" into integration List of files: /rk3399_ARM-atf/tools/fiptool/Makefile

42fb812a7525682362096d651a3749787b3bd555 - Merge changes from topic "ethos-n" into integration

Tue, 04 Apr 2023 14:16:04 +0000

Merge changes from topic "ethos-n" into integration* changes: docs(maintainers): update NPU driver files docs(ethos-n): update porting-guide.rst for NPU feat(ethos-n): add separate RO and RW NSAIDs feat(ethos-n)!: add protected NPU firmware setup feat(ethos-n): add stream extends and attr support feat(ethos-n): add reserved memory address support feat(ethos-n): add event and aux control support feat(ethos-n): add SMC call to get FW properties refactor(ethos-n): split up SMC call handling feat(ethos-n): add NPU firmware validation feat(ethos-n): add check for NPU in SiP setup feat(ethos-n)!: load NPU firmware at BL2 feat(juno): support ARM_IO_IN_DTB option for Juno fix(fconf): fix FCONF_ARM_IO_UUID_NUMBER value fix(fvp): incorrect UUID name in FVP tb_fw_config fix(ethos-n): add workaround for erratum 2838783 feat(ethos-n): add support for NPU to cert_create feat(ethos-n): add NPU support in fiptool feat(ethos-n): add support to set up NSAID build(fiptool): add object dependency generation feat(ethos-n): add NPU sleeping SMC call feat(ethos-n): add multiple asset allocators feat(ethos-n): add reset type to reset SMC calls feat(ethos-n): add protected NPU TZMP1 regions build(ethos-n): add TZMP1 build flag List of files: /rk3399_ARM-atf/tools/fiptool/Makefile

0165ddd7c06fe2d0556865fce89ced8694e3812e - build(fiptool): add object dependency generation

Thu, 08 Dec 2022 16:07:06 +0000

build(fiptool): add object dependency generationThe object target in the fiptool Makefile only depends on thecorresponding source file so it won't rebuild the object, if a headerfile used by the source file is changed.To make it rebuild the object file for both source and header filechanges, a dependency file will now be generated for each object andincluded in the Makefile.Signed-off-by: Mikael Olsson Change-Id: I0468c6e9c54126242150667268d471f28e011b0d List of files: /rk3399_ARM-atf/tools/fiptool/Makefile

034a2e3ef8a9e8e58f7cb7fab6db4ee60b2f9c29 - refactor(fiptool): move plat_fiptool.mk to tools

Wed, 01 Feb 2023 15:55:08 +0000

refactor(fiptool): move plat_fiptool.mk to toolsMove all plat_fiptool.mks into tools, change the logic to recursivelycheck for tools/fiptool/plat_fiptool//plat_fiptool.mkI.e. for a platform that has the path "plat/arm/board/tc/platform.mk",the makefile will now load the first existing file from: - tools/fiptool/plat_fiptool/arm/board/tc/plat_fiptool.mk - tools/fiptool/plat_fiptool/arm/board/plat_fiptool.mk - tools/fiptool/plat_fiptool/arm/plat_fiptool.mkThis enables fiptool to support multiple platforms, or a specific one.Remove file-copying previously being used to handle old default path.Remove custom file cleaning in plat_fiptool.mk.Change-Id: I95245bcf7143b329481d4394ab64f29bfe9de5abSigned-off-by: Raef Coles List of files: /rk3399_ARM-atf/tools/fiptool/Makefile