From: "Denys Dmytriyenko" <denis@denix.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: meta-arm@lists.yoctoproject.org, pbarker@konsulko.com,
wmills@ti.com, daniel.thompson@linaro.org
Subject: Re: [PATCH 3/4] external-arm-toolchain: Add README
Date: Thu, 4 Jun 2020 14:47:00 -0400 [thread overview]
Message-ID: <20200604184700.GF17660@denix.org> (raw)
In-Reply-To: <1591095894-15178-4-git-send-email-sumit.garg@linaro.org>
On Tue, Jun 02, 2020 at 04:34:53PM +0530, Sumit Garg wrote:
> Document usage details for pre-built Arm toolchains.
>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> ---
> .../external-arm-toolchain/README.md | 50 ++++++++++++++++++++++
> 1 file changed, 50 insertions(+)
> create mode 100644 meta-arm-toolchain/recipes-devtools/external-arm-toolchain/README.md
>
> diff --git a/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/README.md b/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/README.md
> new file mode 100644
> index 0000000..65d1a42
> --- /dev/null
> +++ b/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/README.md
> @@ -0,0 +1,50 @@
> +Pre-built Arm toolchain recipes
> +===============================
> +
> +Introduction
> +------------
> +This layer contains recipes for pre-built Arm toolchain recipes as follows:
> +
> +external-arm-toolchain.bb
> +~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +This recipe provides support for pre-built GNU toolchains targeting processors
> +from the Arm Cortex-A family and implementing the Arm A-profile architecture.
> +
> +Usage
> +^^^^^
> +
> +In order to use any of pre-built Arm toolchain versions (8.2, 8.3, 9.2 and so
> +on), a user needs to download and untar tool-set on host machine at a particular
> +installation path eg: ``/opt/toolchain/``. Then user needs to specify following
> +in ``conf/local.conf`` in order to replace OE toolcahin with pre-built GNU-A
> +toolchain:
> +
> +TCMODE = "external-arm"
> +EXTERNAL_TOOLCHAIN = "<path-to-the-toolchain>"
> +
> +- Eg. for AArch64 (eg. qemuarm64 machine in poky distro)
> + EXTERNAL_TOOLCHAIN = "\
> + <installation-path>/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu \
> + "
> +
> +- Eg. for AArch32 (eg. qemuarm machine in poky distro)
> + EXTERNAL_TOOLCHAIN = "\
> + <installation-path>/gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf \
> + "
> +
> +Supported distros and machines
> +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> +
> +Since this pre-built GNU-A tool-set simply replaces OE toolchain, so it is
> +meant to be distro and machine agnostic as long as one is cross-compiling for
> +Arm A-profile architecture.
> +
> +gcc-arm-none-eabi_<version>.bb
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
gcc-aarch64-none-elf?
Probably need to explain a bit more regarding the differences between
baremetal and Linux toolchains, as currently it can be confusing to some
why there are 2 sets of toolchain recipes...
> +This recipe provides support for pre-built GNU Arm Embedded toolchain for
> +bare-metal software development on devices based on 32-bit Arm Cortex-A,
> +Cortex-R and Cortex-M processors.
> +
> +Supported version: 9-2019-q4-major
> --
> 2.7.4
>
next prev parent reply other threads:[~2020-06-04 18:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 11:04 [PATCH 0/4] external-arm-toolchain: Add support for SDK generation Sumit Garg
2020-06-02 11:04 ` [PATCH 1/4] external-arm-toolchain: Remove glibc locale dependency Sumit Garg
2020-06-04 18:36 ` Denys Dmytriyenko
2020-06-05 14:24 ` Sumit Garg
2020-06-02 11:04 ` [PATCH 2/4] external-arm-toolchain: Refine dev libraies packaging Sumit Garg
2020-06-04 18:42 ` Denys Dmytriyenko
2020-06-05 13:52 ` Sumit Garg
2020-06-08 12:02 ` Paul Barker
2020-06-02 11:04 ` [PATCH 3/4] external-arm-toolchain: Add README Sumit Garg
2020-06-04 18:47 ` Denys Dmytriyenko [this message]
2020-06-05 14:32 ` Sumit Garg
2020-06-08 12:08 ` Paul Barker
2020-06-09 7:03 ` Sumit Garg
2020-06-02 11:04 ` [PATCH 4/4] external-arm-toolchain: Add package specific licenses Sumit Garg
2020-06-08 12:10 ` Paul Barker
2020-06-04 8:00 ` [PATCH 0/4] external-arm-toolchain: Add support for SDK generation Paul Barker
2020-06-04 23:00 ` Denys Dmytriyenko
2020-06-08 11:26 ` Sumit Garg
2020-06-12 6:02 ` [meta-arm] " Denys Dmytriyenko
[not found] ` <1615797D4B360D3B.26163@lists.yoctoproject.org>
2020-06-04 23:10 ` Denys Dmytriyenko
2020-06-05 6:24 ` Richard Purdie
2020-06-05 13:29 ` Sumit Garg
2020-06-05 18:40 ` Denys Dmytriyenko
2020-06-08 11:32 ` Sumit Garg
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=20200604184700.GF17660@denix.org \
--to=denis@denix.org \
--cc=daniel.thompson@linaro.org \
--cc=meta-arm@lists.yoctoproject.org \
--cc=pbarker@konsulko.com \
--cc=sumit.garg@linaro.org \
--cc=wmills@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.