From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Martin Kelly <mkelly@xevo.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Jussi Pakkanen <jpakkane@gmail.com>,
Nirbheek Chauhan <nirbheek.chauhan@gmail.com>
Subject: Re: Issues with meson in cross-compiling environment
Date: Tue, 9 Jan 2018 11:05:48 +0200 [thread overview]
Message-ID: <ee65ca42-3632-8f67-4615-dffd816823fe@linux.intel.com> (raw)
In-Reply-To: <2ce0ac68-4ef4-41f5-c931-81990ecd1d03@xevo.com>
On 01/09/2018 01:51 AM, Martin Kelly wrote:
> Recently, we got meson added to OE-core as part of Yocto (thanks
> Alexander Kanavin!).
As a part of that integration, we've had to add a few patches that fix
problems specific to cross-compilation. You can see them here:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/meson/meson
I'd really like to have them merged upstream, so if you're generally in
favor, I'll submit them (or you can simply take them directly).
Alex
next prev parent reply other threads:[~2018-01-09 9:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 23:51 Issues with meson in SDK with cross-file Martin Kelly
2018-01-09 9:05 ` Alexander Kanavin [this message]
[not found] ` <CADqQcK7e7r_bdqqdg3yWC74jxC1rGEO48aGx3xFP2asu0FSJdg@mail.gmail.com>
2018-01-10 12:37 ` Issues with meson in cross-compiling environment Alexander Kanavin
2018-01-09 9:57 ` Issues with meson in SDK with cross-file Nirbheek Chauhan
[not found] ` <CADqQcK4-=Q3mvKJfhjHbJEUYeTiGq3c7dCAR3E=w+ktr+_7RyA@mail.gmail.com>
2018-01-09 10:06 ` Nirbheek Chauhan
2018-01-09 18:17 ` Martin Kelly
2018-01-09 18:20 ` Martin Kelly
[not found] ` <CAAjYPQ=u2U3f6DrL1KP-RkftD8P3nbASf1YUeeL0PFP6vY=hzQ@mail.gmail.com>
2018-01-09 20:33 ` Martin Kelly
2018-01-11 19:22 ` Martin Kelly
2018-01-11 19:26 ` Khem Raj
2018-01-11 19:33 ` Martin Kelly
2018-01-11 19:53 ` Martin Kelly
2018-01-12 12:35 ` Alexander Kanavin
2018-01-17 17:47 ` Martin Kelly
2018-02-06 23:39 ` Martin Kelly
2018-02-07 2:28 ` Joshua Watt
2018-02-07 17:14 ` Martin Kelly
2018-01-10 12:34 ` Alexander Kanavin
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=ee65ca42-3632-8f67-4615-dffd816823fe@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=jpakkane@gmail.com \
--cc=mkelly@xevo.com \
--cc=nirbheek.chauhan@gmail.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