From: Andrew Fish <afish@apple.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Mike Kinney <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Patch] OvmfPkg: Add XCODE5 statements to fix build break
Date: Fri, 19 May 2017 10:15:34 -0700 [thread overview]
Message-ID: <BDF20C26-22F5-4D32-AD27-9F042BDFF46C@apple.com> (raw)
In-Reply-To: <CAKv+Gu-H+Y55APEEL422SCiDpDj1GmWJRotMq46nH77qptb8RA@mail.gmail.com>
> On May 19, 2017, at 10:02 AM, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>
> On 19 May 2017 at 17:45, Kinney, Michael D <michael.d.kinney@intel.com> wrote:
>> Hi Ard,
>>
>> The order of assignment does not matter. I have tried it
>> both ways and both orders use the XCODE option instead of the
>> GCC option when the XCODE5 tool chain is used.
>>
>
> Interesting. Is this fully specified in any of the EDK2 specs? If not,
> we are relying on an implementation detail of our BaseTools, which I
> guess we'd rather avoid.
>
Ard,
I thought it was specified via Conf/tools_def.txt
*_XCODE5_*_*_FAMILY = GCC
*_XCODE5_*_*_BUILDRULEFAMILY = XCODE
XCODE is set to the GCC family. So basically XCODE overrides GCC if both are present, and XCODE uses GCC if only GCC is present. So the best of both worlds :).
Thanks,
Andrew Fish
next prev parent reply other threads:[~2017-05-19 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 6:30 [Patch] OvmfPkg: Add XCODE5 statements to fix build break Michael Kinney
2017-05-19 8:21 ` Laszlo Ersek
2017-05-19 8:32 ` Ard Biesheuvel
2017-05-19 16:45 ` Kinney, Michael D
2017-05-19 17:02 ` Ard Biesheuvel
2017-05-19 17:15 ` Andrew Fish [this message]
2017-05-19 17:24 ` Kinney, Michael D
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-list 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=BDF20C26-22F5-4D32-AD27-9F042BDFF46C@apple.com \
--to=devel@edk2.groups.io \
/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: link
Be 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