From: "Philippe Mathieu-Daudé" <philmd@redhat.com> To: qemu-trivial@nongnu.org, Laszlo Ersek <lersek@redhat.com>, qemu-devel@nongnu.org Cc: "Laurent Vivier" <laurent@vivier.eu>, "Michael Tokarev" <mjt@tls.msk.ru>, "Philippe Mathieu-Daudé" <philmd@redhat.com> Subject: [Qemu-devel] [PATCH v2 1/2] roms: Correct the EDK2_BASETOOLS_OPTFLAGS variable description Date: Sat, 4 May 2019 15:35:39 +0200 [thread overview] Message-ID: <20190504133540.19758-2-philmd@redhat.com> (raw) In-Reply-To: <20190504133540.19758-1-philmd@redhat.com> In commit 1cab464136b4 we incorrectly described the EDK2_BASETOOLS_OPTFLAGS can pass CPPFLAGS and CFLAGS options to the EDK2 build tools, but it only expands the CFLAGS (not to the CPPFLAGS). Update the description to be more accurate. Reported-by: Laszlo Ersek <lersek@redhat.com> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com> --- roms/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roms/Makefile b/roms/Makefile index 0ce84a45ad5..f020102c866 100644 --- a/roms/Makefile +++ b/roms/Makefile @@ -121,8 +121,8 @@ build-efi-roms: build-pxe-roms $(patsubst %,bin-i386-efi/%.efidrv,$(pxerom_targets)) \ $(patsubst %,bin-x86_64-efi/%.efidrv,$(pxerom_targets)) -# Build scripts can pass compiler/linker flags to the EDK2 build tools -# via the EDK2_BASETOOLS_OPTFLAGS (CPPFLAGS and CFLAGS) and +# Build scripts can pass compiler/linker flags to the EDK2 +# build tools via the EDK2_BASETOOLS_OPTFLAGS (CFLAGS) and # EDK2_BASETOOLS_LDFLAGS (LDFLAGS) environment variables. # # Example: -- 2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: "Philippe Mathieu-Daudé" <philmd@redhat.com> To: qemu-trivial@nongnu.org, Laszlo Ersek <lersek@redhat.com>, qemu-devel@nongnu.org Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>, "Michael Tokarev" <mjt@tls.msk.ru>, "Laurent Vivier" <laurent@vivier.eu> Subject: [Qemu-devel] [PATCH v2 1/2] roms: Correct the EDK2_BASETOOLS_OPTFLAGS variable description Date: Sat, 4 May 2019 15:35:39 +0200 [thread overview] Message-ID: <20190504133540.19758-2-philmd@redhat.com> (raw) Message-ID: <20190504133539.qbHoBdXi25JXwMwgCOX42oRUGwK-GKKa3OTgS9JAlBU@z> (raw) In-Reply-To: <20190504133540.19758-1-philmd@redhat.com> In commit 1cab464136b4 we incorrectly described the EDK2_BASETOOLS_OPTFLAGS can pass CPPFLAGS and CFLAGS options to the EDK2 build tools, but it only expands the CFLAGS (not to the CPPFLAGS). Update the description to be more accurate. Reported-by: Laszlo Ersek <lersek@redhat.com> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com> --- roms/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roms/Makefile b/roms/Makefile index 0ce84a45ad5..f020102c866 100644 --- a/roms/Makefile +++ b/roms/Makefile @@ -121,8 +121,8 @@ build-efi-roms: build-pxe-roms $(patsubst %,bin-i386-efi/%.efidrv,$(pxerom_targets)) \ $(patsubst %,bin-x86_64-efi/%.efidrv,$(pxerom_targets)) -# Build scripts can pass compiler/linker flags to the EDK2 build tools -# via the EDK2_BASETOOLS_OPTFLAGS (CPPFLAGS and CFLAGS) and +# Build scripts can pass compiler/linker flags to the EDK2 +# build tools via the EDK2_BASETOOLS_OPTFLAGS (CFLAGS) and # EDK2_BASETOOLS_LDFLAGS (LDFLAGS) environment variables. # # Example: -- 2.20.1
next prev parent reply other threads:[~2019-05-04 13:35 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-04 13:35 [Qemu-devel] [PATCH v2 0/2] roms: Add 'clean' make rule and EDK2 documentation fix Philippe Mathieu-Daudé 2019-05-04 13:35 ` Philippe Mathieu-Daudé 2019-05-04 13:35 ` Philippe Mathieu-Daudé [this message] 2019-05-04 13:35 ` [Qemu-devel] [PATCH v2 1/2] roms: Correct the EDK2_BASETOOLS_OPTFLAGS variable description Philippe Mathieu-Daudé 2019-05-06 14:04 ` Laszlo Ersek 2019-05-06 14:17 ` Philippe Mathieu-Daudé 2019-05-04 13:35 ` [Qemu-devel] [PATCH v2 2/2] roms: List and describe the Makefile 'clean' rule Philippe Mathieu-Daudé 2019-05-04 13:35 ` Philippe Mathieu-Daudé 2019-05-06 14:10 ` Laszlo Ersek
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190504133540.19758-2-philmd@redhat.com \ --to=philmd@redhat.com \ --cc=laurent@vivier.eu \ --cc=lersek@redhat.com \ --cc=mjt@tls.msk.ru \ --cc=qemu-devel@nongnu.org \ --cc=qemu-trivial@nongnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).