From: Denys Dmytriyenko <denis@denix.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: basic bitbake commands to create an SDK?
Date: Tue, 25 Oct 2016 14:29:39 -0400 [thread overview]
Message-ID: <20161025182939.GE2494@denix.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1610221251550.7526@localhost.localdomain>
On Sat, Oct 22, 2016 at 12:53:24PM -0400, Robert P. J. Day wrote:
> On Sat, 22 Oct 2016, Khem Raj wrote:
>
> > generally meta-toolchain is prior art. You want to use image
> > specific SDKs so -cpopulate_sdk <image> is fine. In this case it
> > will include the needed dev headers/libs in your SDK for that given
> > image automatically it can be any image
>
> ah, good to know, i was starting to get that impression from the
> readings. (is there any mention in the docs that meta-toolchain is
> deprecated? if that's the correct word.)
It's not really depricated! It's still useful in cases when you need a
standalone toolchain that is not based on any specific image recipe.
It's prone to errors and more complicated for beginners, hence the new "-c
populate_sdk" method is recommended by default, unless you know what you
are doing...
> > I would recommend to try using eSDK, which can be generated using
> > -cpopulate_sdk_ext see
> >
> > https://wiki.yoctoproject.org/wiki/Application_Development_with_Extensible_SDK
>
> i was just perusing the testsdk.bbclass file, where i read at the
> top:
>
> # testsdk.bbclass enables testing for SDK and Extensible SDK
> #
> # For run SDK tests you need to do,
> # - bitbake core-image-sato -c populate_sdk
> # - bitbake core-image-sato -c testsdk
> #
> # For run eSDK tests you need to do,
> # - bitbake core-image-sato -c populate_sdk_ext
> # - bitbake core-image-sato -c testsdkext
>
> does that testing actually require the core-image-sato image? that's
> certainly what those comments seem to suggest.
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2016-10-25 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 16:05 basic bitbake commands to create an SDK? Robert P. J. Day
2016-10-22 16:37 ` Khem Raj
2016-10-22 16:53 ` Robert P. J. Day
2016-10-22 16:55 ` Khem Raj
2016-10-22 17:03 ` Robert P. J. Day
2016-10-25 18:29 ` Denys Dmytriyenko [this message]
2016-10-22 17:24 ` Robert P. J. Day
2016-10-25 1:01 ` Paul Eggleton
2016-10-24 9:51 ` Robert P. J. Day
2016-10-25 2:18 ` Paul Eggleton
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=20161025182939.GE2494@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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