From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [meson][PATCH] meson: Allow for llvm-native tools to be used
Date: Thu, 2 Jan 2020 17:28:19 +0000 [thread overview]
Message-ID: <b7967f2c-9b56-17fe-76c0-af98b85fcbc0@intel.com> (raw)
In-Reply-To: <54a01022886647f9baa8608f8a6af5b1@XBOX03.axis.com>
On 27/12/2019 12:03, Peter Kjellerstedt wrote:
> If we’re adding a --native-file, shouldn’t it always be specified,
> regardless of --cross-file?
>
> Also, it looks as most of what is currently done in
> override_native_tools() and meson_do_configure_prepend_class-native()
> could be moved to the native-file (the exception seems to be the
> unsetting of CPPFLAGS, CFLAGS, CXXFLAGS and LDFLAGS).
Right, I've had a mental TODO for this for some time but haven't got
around to it.
Ross
prev parent reply other threads:[~2020-01-02 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 11:49 [meson][PATCH] meson: Allow for llvm-native tools to be used fdk17
2019-12-25 12:02 ` ✗ patchtest: failure for " Patchwork
2019-12-27 12:03 ` [meson][PATCH] " Peter Kjellerstedt
2019-12-27 14:25 ` fdk17
2019-12-27 14:30 ` Fred Baksik
2020-01-02 17:28 ` Ross Burton [this message]
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=b7967f2c-9b56-17fe-76c0-af98b85fcbc0@intel.com \
--to=ross.burton@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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