From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Prem Kumar <perry.prem@gmail.com>
Cc: "Gao, Liming" <liming.gao@intel.com>,
edk2-buildtools-devel@lists.sourceforge.net,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-buildtools] Configuration changes for building EDK2 for AARCH64 using LLVM
Date: Mon, 5 Nov 2018 11:22:30 +0100 [thread overview]
Message-ID: <CAKv+Gu_pzUfPBRnnsMtxDAJa6suptyGPZX=MjZQbjHS4gxwhdQ@mail.gmail.com> (raw)
In-Reply-To: <CAG+YCe0WK8V8rHY=khGUBpzrffhx93eYuNSfwYtkT7JLJkxREQ@mail.gmail.com>
On 5 November 2018 at 09:51, Prem Kumar <perry.prem@gmail.com> wrote:
> Hi All,
>
> I'm trying to build EDK2 for AARCH64 using LLVM tool chain under Windows
> environment.
>
>
>
> Kindly provide any pointers
>
> - To configure tools chain,
>
> - Modify Conf folder for LLVM
>
> - Configure for building ARM and AARCH64
>
>
> Any pointers are welcome to proceed further.
>
I'm sorry - I don't have access to a Windows machine, but I am not
aware of any reasons why clang for windows wouldn't work with the
CLANG38 toolchain profile to build AARCH64 targets.
However, GCC5 is by far the best supported one, so if you're after the
ability to build AARCH64 targets using whichever toolchain, that is
what I would recommend instead.
next prev parent reply other threads:[~2018-11-05 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG+YCe0inGqy_60B2LQhAfj0i9nJwMT0Jn0ynZ71TfPUtMUoUA@mail.gmail.com>
[not found] ` <CAG+YCe2ijxfGKKNk6HgW8Et7fL4xSgeJoKqkxnGVeUkes2F1qg@mail.gmail.com>
[not found] ` <4A89E2EF3DFEDB4C8BFDE51014F606A14E3644F3@SHSMSX104.ccr.corp.intel.com>
[not found] ` <CAG+YCe2ROe1wvF5QMX7ZEvLFuuy-1XxwPa=087W7jFny1wZ9zQ@mail.gmail.com>
2018-11-05 8:51 ` [edk2-buildtools] Configuration changes for building EDK2 for AARCH64 using LLVM Prem Kumar
2018-11-05 9:52 ` Gao, Liming
2018-11-05 10:22 ` Ard Biesheuvel [this message]
2018-11-05 10:39 ` Prem Kumar
2018-11-05 10:43 ` Ard Biesheuvel
2018-11-05 14:35 ` Gao, Liming
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='CAKv+Gu_pzUfPBRnnsMtxDAJa6suptyGPZX=MjZQbjHS4gxwhdQ@mail.gmail.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