From: Adrian Freihofer <adrian.freihofer@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: About scripts/oe-find-native-sysroot
Date: Thu, 09 Mar 2017 23:33:18 +0100 [thread overview]
Message-ID: <1489098798.1925.1.camel@gmail.com> (raw)
In-Reply-To: <1488412401.24526.48.camel@linuxfoundation.org>
Hi,
scripts/runqemu-gen-tapdevs requires native sysroot as a command line
parameter. Which folder might be passed to the script now?
Regards,
Adrian
On Wed, 2017-03-01 at 23:53 +0000, Richard Purdie wrote:
> On Wed, 2017-03-01 at 13:58 +0800, Robert Yang wrote:
> > Hi RP,
> >
> > The common STAGING_DIR_NATIVE is gone, so the OECORE_NATIVE_SYSROOT
> > defined in scripts/oe-find-native-sysroot doesn't make any sense
> > currently:
> >
> > OECORE_NATIVE_SYSROOT=`bitbake -e | grep ^STAGING_DIR_NATIVE | cut
> > -d
> > '"' -f2`
> >
> > But the following ones depend on it:
> >
> > meta/classes/populate_sdk_ext.bbclass
> > meta/recipes-devtools/qemu/nativesdk-qemu-helper_1.0.bb
> > scripts/oe-run-native
> > scripts/runqemu-export-rootfs
> > scripts/runqemu-extract-sdk
> >
> > What shall we do on oe-find-native-sysroot? Remove it and
> > make other ones work without it? Or let it depend on build-
> > sysroots,
> > please ?
>
> If we could make other things survive without it that would be good.
> Some might want to use the addto_recipe_sysroot task:
>
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ce79111e73552954
> 6e8a20e4315e3566a556a936
>
> In some cases build-sysroots would likely make the most sense.
>
> Cheers,
>
> Richard
next prev parent reply other threads:[~2017-03-09 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 5:58 About scripts/oe-find-native-sysroot Robert Yang
2017-03-01 23:53 ` Richard Purdie
2017-03-09 22:33 ` Adrian Freihofer [this message]
2017-03-09 22:37 ` Richard Purdie
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=1489098798.1925.1.camel@gmail.com \
--to=adrian.freihofer@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