From: Luca Boccassi <bluca@debian.org>
To: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Cc: jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com
Subject: Re: [RFC PATCH] RFC build: prototype support for ARM builds
Date: Tue, 19 Dec 2017 13:27:07 +0000 [thread overview]
Message-ID: <1513690027.25709.75.camel@debian.org> (raw)
In-Reply-To: <20171219105338.198727-1-bruce.richardson@intel.com>
On Tue, 2017-12-19 at 10:53 +0000, Bruce Richardson wrote:
> Add some skeleton files to enable compiling for ARM target. This has
> been
> tested by doing a cross-compile for armv8-a type using the linaro gcc
> toolchain.
>
> meson arm-build --cross-file aarch64_cross.txt
> ninja -C arm-build
>
> where aarch64_cross.txt contained the following
>
> [binaries]
> c = 'aarch64-linux-gnu-gcc'
> cpp = 'aarch64-linux-gnu-cpp'
> ar = 'aarch64-linux-gnu-ar'
>
> [host_machine]
> system = 'linux'
> cpu_family = 'aarch64'
> cpu = 'armv8-a'
> endian = 'little'
>
> It is hoped that those working on arm architecture can use this as a
> baseline
> to add arm support - both native compiled and cross-compiled - to the
> meson
> build.
Can't comment on ARM functionality, but shouldn't the new files use
SPDX ids rather than the full license header?
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2017-12-19 13:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 10:53 [RFC PATCH] RFC build: prototype support for ARM builds Bruce Richardson
2017-12-19 13:27 ` Luca Boccassi [this message]
2017-12-19 14:17 ` Bruce Richardson
2018-01-19 13:05 ` [PATCH v2 1/2] build: add " Pavan Nikhilesh
2018-01-19 13:05 ` [PATCH v2 2/2] build: add support for detecting march on ARM Pavan Nikhilesh
2018-01-19 13:52 ` [PATCH v3 1/2] build: add support for ARM builds Pavan Nikhilesh
2018-01-19 13:52 ` [PATCH v3 2/2] build: add support for detecting march on ARM Pavan Nikhilesh
2018-01-19 16:17 ` Bruce Richardson
2018-01-19 17:13 ` Pavan Nikhilesh
2018-01-19 17:30 ` Bruce Richardson
2018-01-19 16:24 ` [PATCH v3 1/2] build: add support for ARM builds Bruce Richardson
2018-01-19 16:49 ` Hemant Agrawal
2018-01-19 17:33 ` Bruce Richardson
2018-01-19 18:23 ` [PATCH v4 " Pavan Nikhilesh
2018-01-19 18:23 ` [PATCH v4 2/2] build: add support for detecting march on ARM Pavan Nikhilesh
2018-01-22 5:52 ` Herbert Guan
2018-01-22 7:16 ` Pavan Nikhilesh
2018-01-22 11:46 ` [PATCH v5 1/2] build: add support for ARM builds Pavan Nikhilesh
2018-01-22 11:46 ` [PATCH v5 2/2] build: add support for detecting march on ARM Pavan Nikhilesh
2018-01-22 12:30 ` Bruce Richardson
2018-01-22 12:37 ` Pavan Nikhilesh
2018-01-22 14:09 ` Bruce Richardson
2018-01-22 14:44 ` Pavan Nikhilesh
2018-01-22 15:26 ` [PATCH v6 1/4] build: add support for ARM builds Pavan Nikhilesh
2018-01-22 15:26 ` [PATCH v6 2/4] build: add support for detecting march on ARM Pavan Nikhilesh
2018-01-22 15:26 ` [PATCH v6 3/4] build: add support for vendor specific ARM cross builds Pavan Nikhilesh
2018-01-22 15:26 ` [PATCH v6 4/4] doc: add instructions to cross compile using meson Pavan Nikhilesh
2018-01-22 16:10 ` [PATCH v6 1/4] build: add support for ARM builds Bruce Richardson
2018-01-22 16:20 ` Jerin Jacob
2018-01-22 16:26 ` Bruce Richardson
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=1513690027.25709.75.camel@debian.org \
--to=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.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 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).