All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Martin Kelly <mkelly@xevo.com>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] meson: export native env only for native build
Date: Wed, 15 Nov 2017 12:05:44 +0200	[thread overview]
Message-ID: <4f3b5824-0625-ad62-95fa-8b1fae4a9c24@linux.intel.com> (raw)
In-Reply-To: <a07f0309-e598-0188-58a6-8592fdf036a0@xevo.com>

On 11/14/2017 08:23 PM, Martin Kelly wrote:

> For native builds:
> - Keep the defaults (which use native tools), but export 
> PKG_CONFIG=pkg-config-native instead of pkg-config.
> 
> For target builds:
> - Set CC, CXX, LD, and AR, but *not* CFLAGS, CXXFLAGS, LDFLAGS etc. We 
> need CC, CXX etc. so meson finds the native tools for its build sanity 
> tests, but we don't want to set the flags, as meson will slurp them in 
> and apply them to the cross build. Note that even though we set CC, etc. 
> meson will correctly override them in the cross file for the actual 
> target build.

Thanks for looking - can you make a patch for these things against my 
branch in poky-contrib, and send it to oe-core list? I will send the 
patchset any day now, and there will be a corresponding patch to remove 
meson recipe and class from meta-oe. So now is the good point to have it 
all fixed so that the transition is smooth.


Alex


  reply	other threads:[~2017-11-15 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 19:27 [meta-oe][PATCH] meson: export native env only for native build Martin Kelly
2017-11-14 12:36 ` Alexander Kanavin
2017-11-14 18:23   ` Martin Kelly
2017-11-15 10:05     ` Alexander Kanavin [this message]
2017-11-15 17:23       ` Martin Kelly

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=4f3b5824-0625-ad62-95fa-8b1fae4a9c24@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=mkelly@xevo.com \
    --cc=openembedded-devel@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 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.