Changes in Makefile

249fb06c3df6cd40ff2566f29c672366c0f0f863 - Merge "refactor(build): avoid implicit pattern rules" into integration

Thu, 09 Oct 2025 12:51:30 +0000

Merge "refactor(build): avoid implicit pattern rules" into integration List of files: /rk3399_ARM-atf/tools/sptool/Makefile

a4ac07c7a553b00a48219823e543c96828c99186 - refactor(build): avoid implicit pattern rules

Tue, 04 Jun 2024 11:56:00 +0000

refactor(build): avoid implicit pattern rulesThis change translates any implicit pattern rules into the equivalentstatic pattern rules, i.e. rules like: %.o: %.s ...... become: $(OBJS): %.o: %.s ...These behave similarly, but have some subtle differences. The formerdefines a rule "for any target matching %.o where there is not a morespecific rule", whereas the latter defines a rule "for these targets,which match %.o".Where possible it is better to use a static pattern rule as it reducesthe rule space that Make needs to search.Change-Id: Ifba4f44bcecf4e74980c31347e192cdf1e42003eSigned-off-by: Chris Kay List of files: /rk3399_ARM-atf/tools/sptool/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/sptool/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/sptool/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/sptool/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/sptool/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/sptool/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/sptool/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/sptool/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/sptool/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/sptool/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/sptool/Makefile

76a08094c53faac3250b845dc12b4884f7e42d84 - Merge "tools: Set the tool's default binary name" into integration

Thu, 10 Sep 2020 19:00:20 +0000

Merge "tools: Set the tool's default binary name" into integration List of files: /rk3399_ARM-atf/tools/sptool/Makefile

b13e3f9f98d08b8583db64d62acd947e727a1a4d - tools: Set the tool's default binary name

Sat, 05 Sep 2020 03:40:41 +0000

tools: Set the tool's default binary nameThis patch: fafd3ec9c assumes that tools must build fromthe main makefile folder.This assumption leads to the error when somebody wants tobuild a tool from the tool's folder.Hence changes are done to provide the default binary namein the tool's makefile.Change-Id: Iae570a7f8d322151376b6feb19e739300eecc3fcSigned-off-by: Manish V Badarkhe List of files: /rk3399_ARM-atf/tools/sptool/Makefile

2b4103f7863f2b9f45029835cc948a53a03b3bdf - Merge "tools: Get the tool's binary name from the main makefile" into integration

Mon, 24 Aug 2020 17:04:33 +0000

Merge "tools: Get the tool's binary name from the main makefile" into integration List of files: /rk3399_ARM-atf/tools/sptool/Makefile

fafd3ec9c954cbc5430dc24bdf5c46b97034c832 - tools: Get the tool's binary name from the main makefile

Thu, 13 Aug 2020 04:56:33 +0000

tools: Get the tool's binary name from the main makefileCurrently, the tool's makefile override the tool's binary namewhich is already been defined in the main makefile.Hence fix is provided so that the tool's makefile get the tool'sbinary name from the main makefile instead of overriding it.Change-Id: I8af2bd391a96bba2dbcddef711338a94ebf5f038Signed-off-by: Manish V Badarkhe List of files: /rk3399_ARM-atf/tools/sptool/Makefile

fca0a51ff5a710c10f4512f07d88b2e828774a3a - Merge pull request #1707 from antonio-nino-diaz-arm/an/spm

Tue, 11 Dec 2018 16:48:17 +0000

Merge pull request #1707 from antonio-nino-diaz-arm/an/spmSPM: Initial prototype based on SPCI and SPRT List of files: /rk3399_ARM-atf/tools/sptool/Makefile

26010da11629f27ddf013ba6127198b33edcd574 - SPM: sptool: Introduce tool to package SP and RD

Tue, 27 Nov 2018 14:58:04 +0000

SPM: sptool: Introduce tool to package SP and RDThis tool packages Secure Partitions and Resource Descriptor blobs intoa simple file that can be loaded by SPM.Change-Id: If3800064f30bdc3d7fc6a15ffbb3007ef632bcaaSigned-off-by: Antonio Nino Diaz List of files: /rk3399_ARM-atf/tools/sptool/Makefile