Changes in Makefile

628749115565bc73225c62b09bef4d253ea79b43 - Merge "feat(st): put stm32image tool in build directory" into integration

Tue, 08 Jul 2025 16:53:07 +0000

Merge "feat(st): put stm32image tool in build directory" into integration List of files: /rk3399_ARM-atf/tools/stm32image/Makefile

0b4722cf261829596f82f92d62aced48c95ccd83 - feat(st): put stm32image tool in build directory

Tue, 08 Jul 2025 12:09:34 +0000

feat(st): put stm32image tool in build directoryFollowing the series moving common tools compilation to the builddirectory[1], do the same for stm32image tool.[1]: cbd6cec3c3 feat(build): put fiptool in the build directorySigned-off-by: Yann Gautier Change-Id: If33556e98c4788350a29c8ad96dc574584b67abd List of files: /rk3399_ARM-atf/tools/stm32image/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/stm32image/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/stm32image/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/stm32image/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/stm32image/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/stm32image/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/stm32image/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/stm32image/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/stm32image/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/stm32image/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/stm32image/Makefile

52a9e53b8cf253cdcd73265df60d9e8b03e534df - Merge pull request #1612 from antonio-nino-diaz-arm/an/tools

Wed, 10 Oct 2018 13:00:14 +0000

Merge pull request #1612 from antonio-nino-diaz-arm/an/toolstools: Make invocation of host compiler correct List of files: /rk3399_ARM-atf/tools/stm32image/Makefile

750e8d807dced6cd2a523aad7be74161dc705f6e - tools: Make invocation of host compiler correct

Thu, 04 Oct 2018 13:35:38 +0000

tools: Make invocation of host compiler correctHOSTCC should be used in any of the tools inside the tools/ directoryinstead of CC. That way it is possible to override both values from thecommand line when building the Trusted Firmware and the tools at thesame time. Also, use HOSTCCFLAGS instead of CFLAGS.Also, instead of printing the strings CC and LD in the console duringthe compilation of the tools, HOSTCC and HOSTLD have to be used forclarity. This is how it is done in other projects like U-Boot or Linux.Change-Id: Icd6f74c31eb74cdd1c353583399ab19e173e293eSigned-off-by: Antonio Nino Diaz List of files: /rk3399_ARM-atf/tools/stm32image/Makefile

3989a81930c72d19f660262ec7f280b2bbd6f111 - Merge pull request #1609 from MISL-EBU-System-SW/integration-ble

Thu, 04 Oct 2018 13:31:58 +0000

Merge pull request #1609 from MISL-EBU-System-SW/integration-bleplat/marvell: Move BLE into the platform tree, minor fix in tools. List of files: /rk3399_ARM-atf/tools/stm32image/Makefile

c0f73edc9b04023a24a1e2103b442a94297921a7 - tools: Fix broken object compilation rules

Tue, 02 Oct 2018 07:28:00 +0000

tools: Fix broken object compilation rulesAs these rules depend on non-existing headers as well (likely copy &pasted from fiptool), they never matched, and the built-in rules wereused. That led to random breakages when e.g. CPPFLAGS was suddenlyevaluated and contained invalid options.For the stm32image, this reveals that we were relying on the built-inrules by passing -D_GNU_SOURCE via CPPFLAGS, rather than using CFLAGS asused in the local rule. Fix that as well.Signed-off-by: Jan Kiszka List of files: /rk3399_ARM-atf/tools/stm32image/Makefile

d87d524ee4482c00a15f6d72c6fe5ab02f5f4746 - Merge pull request #1466 from Yann-lms/stm32mp1

Wed, 25 Jul 2018 15:05:35 +0000

Merge pull request #1466 from Yann-lms/stm32mp1Add STMicroelectronics STM32MP1 platform support List of files: /rk3399_ARM-atf/tools/stm32image/Makefile

5fbcdd056b51f2ccffee4a0e824df70fb3497323 - tools: Add stm32image tool into TF-A

Thu, 05 Jul 2018 14:50:22 +0000

tools: Add stm32image tool into TF-AThis tools adds a specific header to ST TF-A binary.This header is used by STM32MP1 ROM code to check the bootloader.Signed-off-by: Yann Gautier Signed-off-by: Lionel Debieve List of files: /rk3399_ARM-atf/tools/stm32image/Makefile