From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
Martin Kelly <mkelly@xevo.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/9] gnomebase-meson.bbclass: add a meson-specific version
Date: Thu, 11 Jan 2018 17:49:16 +0000 [thread overview]
Message-ID: <1515692956.29722.122.camel@linuxfoundation.org> (raw)
In-Reply-To: <83efbf54-dde5-2a84-00a0-6db5fc9e7ee5@linux.intel.com>
On Thu, 2018-01-11 at 13:35 +0200, Alexander Kanavin wrote:
> On 01/10/2018 09:11 PM, Martin Kelly wrote:
> >
> > Yes, to be clear, I'm not griping, as I'm very happy meson landed
> > in
> > OE-core, and I'm working on SDK support now. I have an OE-core
> > thread
> > going with meson upstream to get the issue fixed.
> >
> > To be clear though, I'm not sure it even regressed. AFAICT, it
> > never
> > quite worked.
> >
> > Where would I add SDK tests for this?
> meta/lib/oeqa/selftest/cases is the place. Not sure what existing
> SDK
> tests are already there.
Actually, no. See:
$ ls meta/lib/oeqa/sdk/cases/
buildcpio.py
buildgalculator.py
buildlzip.py
gcc.py
perl.py
python.py
There is also "sdkext" for the eSDK.
You'd run these with:
INHERIT += "testimage"
and then
bitbake <sdk-target> -c testsdk
Cheers,
Richard
next prev parent reply other threads:[~2018-01-11 17:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 13:12 [PATCH 1/9] meson: add a recipe and class from meta-oe Alexander Kanavin
2018-01-04 13:12 ` [PATCH 2/9] gnomebase-meson.bbclass: add a meson-specific version Alexander Kanavin
2018-01-05 11:47 ` Burton, Ross
2018-01-05 14:57 ` Alexander Kanavin
2018-01-10 17:55 ` Martin Kelly
2018-01-10 18:48 ` Richard Purdie
2018-01-10 19:11 ` Martin Kelly
2018-01-11 11:35 ` Alexander Kanavin
2018-01-11 17:49 ` Richard Purdie [this message]
2018-01-11 19:26 ` Martin Kelly
2018-01-04 13:12 ` [PATCH 3/9] json-glib: convert to meson build Alexander Kanavin
2018-01-04 13:12 ` [PATCH 4/9] libepoxy: " Alexander Kanavin
2018-01-04 13:12 ` [PATCH 5/9] libinput: " Alexander Kanavin
2018-01-04 13:12 ` [PATCH 6/9] sysprof: " Alexander Kanavin
2018-01-04 13:12 ` [PATCH 7/9] gst-player: Upgrade, rename to gst-examples Alexander Kanavin
2018-01-04 13:12 ` [PATCH 8/9] meson: export native env only for native build Alexander Kanavin
2018-01-04 13:12 ` [PATCH 9/9] meson: Port pkgconfig-native patch to 0.44.0 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=1515692956.29722.122.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=mkelly@xevo.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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