public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Vin Xue <vinxue@outlook.com>
To: Leif Lindholm <leif@nuviainc.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-platforms][PATCH] Readme.md: Update cross compiling section
Date: Wed, 15 Jul 2020 10:31:23 +0000	[thread overview]
Message-ID: <SL2PR03MB4442F8AA4BB204862EF194A4C57E0@SL2PR03MB4442.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <20200715092654.GD12303@vanye>

[-- Attachment #1: Type: text/plain, Size: 4190 bytes --]

Hi Lindholm,

Thanks for your comments.
Usually, I am working on Windows PC for BIOS development.
Today I tried to build edk2-platform AAarch64 code, and found it's not
easy to follow readme document. So, I submitted the patch.

Please drop the patch if there is a better update in the near future.

________________________________
From: Leif Lindholm <leif@nuviainc.com>
Sent: Wednesday, July 15, 2020 5:26 PM
To: Vin Xue <vinxue@outlook.com>
Cc: devel@edk2.groups.io <devel@edk2.groups.io>; Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-platforms][PATCH] Readme.md: Update cross compiling section

On Wed, Jul 15, 2020 at 14:05:03 +0800, Vin Xue wrote:
> 1. Update invalid URL link of Linaro GCC toolchains.
> 2. Add build command example for cross compiling.
>
> Cc: Leif Lindholm <leif@nuviainc.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Signed-off-by: Vin Xue <vinxue@outlook.com>
> ---
>  Readme.md | 14 ++++++++++----
>  1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/Readme.md b/Readme.md
> index ea9492240a..2e30f672cc 100644
> --- a/Readme.md
> +++ b/Readme.md
> @@ -57,10 +57,13 @@ X64                 | x86_64-linux-gnu-
>
>  ### GCC
>  Linaro provides GCC toolchains for
> -[aarch64-linux-gnu](https://releases.linaro.org/components/toolchain/binaries/latest/aarch64-linux-gnu/)
> -and [arm-linux-gnueabihf](https://releases.linaro.org/components/toolchain/binaries/latest/arm-linux-gnueabihf/)
> -compiled to run on x86_64/i686 Linux and i686 Windows. Some Linux distributions
> -provide their own packaged cross-toolchains.
> +[aarch64-linux-gnu](https://releases.linaro.org/components/toolchain/binaries/latest-7/aarch64-linux-gnu/)
> +and [arm-linux-gnueabihf](https://releases.linaro.org/components/toolchain/binaries/latest-7/arm-linux-gnueabihf/)
> +compiled to run on x86_64/i686 Linux and i686 Windows.

Yes, we should update the information about the Windows toolchains.
But gcc 7 is ancient. If we go to
https://releases.linaro.org/components/toolchain/binaries/, we see
they have added a gcc-8 "directory". I say "directory" with quotes
because clicking on that redirects you to
https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads
This is the location we should now be pointing to - and these
toolchains are now gcc 9.2.

> +
> +Some Linux distributions provide their own packaged cross-toolchains. e.g. Install AArch64 GCC toolchain on Ubuntu (x86_64) with:
> +
> +`sudo apt install gcc-aarch64-linux-gnu`

We can't maintain a list of every possible package name with every
possible package install command (apt, yum, dnf, pacman, ?) for every
distribution (debian, ubuntu, redhat, fedora, centos, suse, arch,
gentoo, ?) out there. We'll also be adding RISC-V support in the near
future.

The abovementioned arm.com link includes prebuilt compilers for
Windows-x86_64, Linux-x86_64, and Linux-AArch64 (for AArch32).
Anyone unable to figure out how to find and install packages provided
with their distro can always grab a toolchain from that download page.

>
>  ### clang
>  Clang does not require separate cross compilers, but it does need a
> @@ -160,6 +163,9 @@ variable `{TOOL_CHAIN_TAG}_{TARGET_ARCH}_PREFIX` - in the case above,
>  **GCC5_AARCH64_PREFIX**.
>
>  So, referring to the cross compiler toolchain table above, we should prepend the `build` command line with `GCC5_AARCH64_PREFIX=aarch64-linux-gnu-`.
> +```
> +$ GCC5_AARCH64_PREFIX=aarch64-linux-gnu- build -n $NUM_CPUS -a AARCH64 -t GCC5 -p Platform/ARM/JunoPkg/ArmJuno.dsc
> +```

How to build a platform is already described in the section
immediately preceding this one. This paragraph tells you how to inform
the build system to apply a prefix for the compiler if cross compiling.

Seprate note (to self, really): we don't need the -n thing anymore,
the 'build' command has been updated to figure this out for itself.

/
    Leif

>
>  ## Using uefi-tools helper scripts
>  uefi-tools is a completely unofficial set of helper-scripts developed by Linaro.
> --
> 2.27.0.windows.1
>

[-- Attachment #2: Type: text/html, Size: 6784 bytes --]

  reply	other threads:[~2020-07-15 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15  6:05 [edk2-platforms][PATCH] Readme.md: Update cross compiling section Vin Xue
2020-07-15  9:26 ` Leif Lindholm
2020-07-15 10:31   ` Vin Xue [this message]
2020-07-15 11:09     ` Leif Lindholm

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=SL2PR03MB4442F8AA4BB204862EF194A4C57E0@SL2PR03MB4442.apcprd03.prod.outlook.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