<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2025</copyright>
    <generator>Java</generator><item>
        <title>249fb06c3df6cd40ff2566f29c672366c0f0f863 - Merge &quot;refactor(build): avoid implicit pattern rules&quot; into integration</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#249fb06c3df6cd40ff2566f29c672366c0f0f863</link>
        <description>Merge &quot;refactor(build): avoid implicit pattern rules&quot; into integration

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Thu, 09 Oct 2025 12:51:30 +0000</pubDate>
        <dc:creator>Chris Kay &lt;chris.kay@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>a4ac07c7a553b00a48219823e543c96828c99186 - refactor(build): avoid implicit pattern rules</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#a4ac07c7a553b00a48219823e543c96828c99186</link>
        <description>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 &quot;for any target matching %.o where there is not a morespecific rule&quot;, whereas the latter defines a rule &quot;for these targets,which match %.o&quot;.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 &lt;chris.kay@arm.com&gt;

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Tue, 04 Jun 2024 11:56:00 +0000</pubDate>
        <dc:creator>Chris Kay &lt;chris.kay@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>555705638ff46b9b9a645c32137a977ffdb429d1 - Merge changes I04ecd50f,I830b53e2 into integration</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#555705638ff46b9b9a645c32137a977ffdb429d1</link>
        <description>Merge changes I04ecd50f,I830b53e2 into integration* changes:  fix(rcar3-drivers): disable A/B loader support by default  fix(rcar-layout): fix tool build

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Thu, 05 Dec 2024 14:06:20 +0000</pubDate>
        <dc:creator>Yann Gautier &lt;yann.gautier@st.com&gt;</dc:creator>
    </item>
<item>
        <title>72f4b70e8e8e656d88bda77605f73076474f5a55 - fix(rcar-layout): fix tool build</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#72f4b70e8e8e656d88bda77605f73076474f5a55</link>
        <description>fix(rcar-layout): fix tool buildSince 2f1c5e7eb177 (&quot;build: use GCC to link by default&quot;) thecode does not even compile with GCC14 on debian/unstable withthe following error:/usr/lib/gcc-cross/aarch64-linux-gnu/14/../../../../aarch64-linux-gnu/bin/ld: bootparam_sa0.elf: error: PHDR segment not covered by LOAD segment/usr/lib/gcc-cross/aarch64-linux-gnu/14/../../../../aarch64-linux-gnu/bin/ld: cert_header_sa6.elf: error: PHDR segment not covered by LOAD segmentFix the tools build.Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;Change-Id: I830b53e23f25c62da3583c1c3e02e0607a237d15

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Sat, 09 Nov 2024 10:43:05 +0000</pubDate>
        <dc:creator>Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;</dc:creator>
    </item>
<item>
        <title>0195bac19b9d150a138bb3eeb2b9d4d4f5097cbd - Merge &quot;build: consolidate directory creation rules&quot; into integration</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#0195bac19b9d150a138bb3eeb2b9d4d4f5097cbd</link>
        <description>Merge &quot;build: consolidate directory creation rules&quot; into integration

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Mon, 29 Jul 2024 13:54:46 +0000</pubDate>
        <dc:creator>Manish Pandey &lt;manish.pandey2@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>f4dd18c270c0a171c1c4a04b1c7e886516ccd235 - build: consolidate directory creation rules</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#f4dd18c270c0a171c1c4a04b1c7e886516ccd235</link>
        <description>build: consolidate directory creation rulesThis commit streamlines directory creation by introducing a singlepattern rule to automatically make directories for which there is adependency.We currently use several macros to generate rules to create directoriesupon dependence, which is a significant amount of code and a lot ofredundancy. The rule introduced by this change represents a catch-all:any rule dependency on a path ending in a forward slash is automaticallycreated.Now, rules can rely on an unordered dependency (`|`) on `$$(@D)/` which,when secondary expansion is enabled, expands to the directory of thetarget being built, e.g.:    build/main.o: main.c | $$(@D)/ # automatically creates `build/`Change-Id: I7e554efa2ac850e779bb302fd9c7fbb239886c9fSigned-off-by: Chris Kay &lt;chris.kay@arm.com&gt;

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Tue, 04 Jun 2024 00:04:48 +0000</pubDate>
        <dc:creator>Chris Kay &lt;chris.kay@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>9b7d72b314e46fdea36215bf5fe323d4bb51c24e - Merge changes from topic &quot;ck/tf-a/target-properties&quot; into integration</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#9b7d72b314e46fdea36215bf5fe323d4bb51c24e</link>
        <description>Merge changes from topic &quot;ck/tf-a/target-properties&quot; into integration* changes:  build(rzg-layout): split combined targets  build(rcar-layout): split combined targets

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Mon, 15 Jul 2024 15:04:59 +0000</pubDate>
        <dc:creator>Manish Pandey &lt;manish.pandey2@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>ea2c6521ca1ba42e00545110ea955fc24606d671 - build(rcar-layout): split combined targets</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#ea2c6521ca1ba42e00545110ea955fc24606d671</link>
        <description>build(rcar-layout): split combined targetsThis is a small change to split up the generation of the R-Car layoutimages into unique targets. This is predominantly for cleanlinessreasons - Make current doesn&apos;t know about the `.bin` and `.srec`binaries generated by the `.elf` target.Change-Id: I624bc0c62e99cead66a6d6e25ff016aecf6b985aSigned-off-by: Chris Kay &lt;chris.kay@arm.com&gt;

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Tue, 04 Jun 2024 11:31:06 +0000</pubDate>
        <dc:creator>Chris Kay &lt;chris.kay@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>cd8eb18d580e9c413ec9e2c33ebf32992ffd31ca - Merge changes from topic &quot;ck/tf-a/verbosity-cleanup&quot; into integration</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#cd8eb18d580e9c413ec9e2c33ebf32992ffd31ca</link>
        <description>Merge changes from topic &quot;ck/tf-a/verbosity-cleanup&quot; 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/renesas/rcar_layout_create/makefile</description>
        <pubDate>Mon, 17 Jun 2024 09:01:49 +0000</pubDate>
        <dc:creator>Manish Pandey &lt;manish.pandey2@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>7c4e1eea61a32291a6640070418e07ab98b42442 - build: unify verbosity handling</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#7c4e1eea61a32291a6640070418e07ab98b42442</link>
        <description>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 &apos;This command is neither echoed nor executed&apos;    $(q)echo &apos;This command is executed but not echoed&apos;When building verbosely, `s` expands to a value which disables thecommand that follows, and `q` expands to nothing:    $(s)echo &apos;This command is neither echoed nor executed&apos;    $(q)echo &apos;This command is executed and echoed&apos;In all other cases, both `s` and `q` expand to a value which suppressesechoing of the command that follows:    $(s)echo &apos;This command is executed but not echoed&apos;    $(q)echo &apos;This command is executed but not echoed&apos;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 &lt;chris.kay@arm.com&gt;

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Thu, 02 May 2024 17:52:37 +0000</pubDate>
        <dc:creator>Chris Kay &lt;chris.kay@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>c97831eb09f47495fc0c9911882f4e152aaa388c - Merge &quot;build: use GCC to link by default&quot; into integration</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#c97831eb09f47495fc0c9911882f4e152aaa388c</link>
        <description>Merge &quot;build: use GCC to link by default&quot; into integration

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Fri, 05 Apr 2024 20:21:15 +0000</pubDate>
        <dc:creator>Bipin Ravi &lt;bipin.ravi@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>2f1c5e7eb1775b252fa4998e10093b8ac34ca699 - build: use GCC to link by default</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#2f1c5e7eb1775b252fa4998e10093b8ac34ca699</link>
        <description>build: use GCC to link by defaultWhen configuring GNU GCC as the C compiler, we usually use the GNU BFDlinker directly to link by default. However, this complicates thingsbecause we also need to support LTO, which can only be done when linkingis done via the C compiler, and we cannot change the linker later on ifsome other part of the build system wants to enable LTO.This change migrates the default choice of linker to GCC if the Ccompiler is GCC, in order to enable this use-case. This should have noimpact on anything outside of the build system, as by default GCC merelyacts as a wrapper around BFD.Change-Id: I40771be2b0571def67bbfde9e877e7629ec8cdaaSigned-off-by: Chris Kay &lt;chris.kay@arm.com&gt;

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Wed, 21 Feb 2024 12:52:46 +0000</pubDate>
        <dc:creator>Chris Kay &lt;chris.kay@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>60dd8069bfa4e65e3320d4ec8f0b6c981f8abaef - Merge &quot;build: use new toolchain variables for tools&quot; into integration</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#60dd8069bfa4e65e3320d4ec8f0b6c981f8abaef</link>
        <description>Merge &quot;build: use new toolchain variables for tools&quot; into integration

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Tue, 20 Feb 2024 15:06:35 +0000</pubDate>
        <dc:creator>Mark Dykes &lt;mark.dykes@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>084c9d3c0de8ed9eb1afd7057c5a2a41c11d9443 - Merge &quot;build: refactor toolchain detection&quot; into integration</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#084c9d3c0de8ed9eb1afd7057c5a2a41c11d9443</link>
        <description>Merge &quot;build: refactor toolchain detection&quot; into integration

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Tue, 20 Feb 2024 15:04:53 +0000</pubDate>
        <dc:creator>Mark Dykes &lt;mark.dykes@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>ffb7742125def3e0acca4c7e4d3215af5ce25a31 - build: use new toolchain variables for tools</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#ffb7742125def3e0acca4c7e4d3215af5ce25a31</link>
        <description>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&apos;re replacing.Change-Id: I644fe4ce82ef1894bed129ddb4b6ab94fb04985dSigned-off-by: Chris Kay &lt;chris.kay@arm.com&gt;

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Mon, 04 Dec 2023 12:03:51 +0000</pubDate>
        <dc:creator>Chris Kay &lt;chris.kay@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>cc277de81692cf72f067354ada6e84f5e996f6b8 - build: refactor toolchain detection</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#cc277de81692cf72f067354ada6e84f5e996f6b8</link>
        <description>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 &quot;role&quot;) 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 &lt;chris.kay@arm.com&gt;

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Fri, 20 Oct 2023 09:17:33 +0000</pubDate>
        <dc:creator>Chris Kay &lt;chris.kay@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>07da4854e919b0d0a217886666aefd95a003829a - Merge changes from topics &quot;rcar-tools-fix&quot;, &quot;toolchain-cleanup&quot; into integration</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#07da4854e919b0d0a217886666aefd95a003829a</link>
        <description>Merge changes from topics &quot;rcar-tools-fix&quot;, &quot;toolchain-cleanup&quot; into integration* changes:  build: remove the `NM` variable  build: prefer `gcc-ar` over `ar`  build: add `--no-warn-rwx-segments` when linking with GCC  build: always use the C compiler to assemble  build: always use the C compiler to preprocess  fix(rcar): fix implicit rule invocations in tools

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Wed, 24 Jan 2024 15:11:22 +0000</pubDate>
        <dc:creator>Lauren Wehrmeister &lt;lauren.wehrmeister@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>e068a7ca860f35a171f608d55fb8a2a00ebd7561 - fix(rcar): fix implicit rule invocations in tools</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#e068a7ca860f35a171f608d55fb8a2a00ebd7561</link>
        <description>fix(rcar): fix implicit rule invocations in toolsThe `rzg_layout_create` and `rcar_layout_create` tools have a rule tobuild object files from C files, but it depends on object files in theparent directory when it should depend on object files in the currentdirectory. Consequently, the rule is not triggering and the implicit Ccompilation rule is executed instead. This rule works, so I havereplaced the broken rule with exactly the same command as what theimplicit rule is executing and fixed the dependency.Change-Id: Ib8d640361adff8c4d660738dda230e5536bec629Signed-off-by: Chris Kay &lt;chris.kay@arm.com&gt;

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Mon, 15 Jan 2024 16:16:07 +0000</pubDate>
        <dc:creator>Chris Kay &lt;chris.kay@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>0a4bf763f3e5b2f67b0d5798a40fb9d0caefd554 - Merge pull request #1914 from marex/arm/master/d3draak-v2.0.1</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#0a4bf763f3e5b2f67b0d5798a40fb9d0caefd554</link>
        <description>Merge pull request #1914 from marex/arm/master/d3draak-v2.0.1Arm/master/d3draak v2.0.1

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Tue, 02 Apr 2019 13:16:27 +0000</pubDate>
        <dc:creator>Antonio Ni&#241;o D&#237;az &lt;antonio.ninodiaz@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>bfbf5df405d5e99d6df1060ab8da479c8f1524ab - rcar_gen3: plat: Add initial D3 support</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile#bfbf5df405d5e99d6df1060ab8da479c8f1524ab</link>
        <description>rcar_gen3: plat: Add initial D3 supportAdd R-Car D3 SoC platform specifics. Driver, PFC, QoS, DDR init codewill be added separately.Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@gmail.com&gt;

            List of files:
            /rk3399_ARM-atf/tools/renesas/rcar_layout_create/makefile</description>
        <pubDate>Sat, 05 Jan 2019 12:56:03 +0000</pubDate>
        <dc:creator>Marek Vasut &lt;marek.vasut+renesas@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
