Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: uniformity in defining basic SDK images?
Date: Mon, 2 Mar 2015 04:30:37 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1503020424530.21001@localhost> (raw)


  reading YP kernel dev manual and section 2.5.1 contains the
following passage:

"Briefly, the kernel-dev package is installed by default on all *.sdk
images... Because all SDK image recipes include dev-pkgs, the
kernel-dev packages will be installed as part of the SDK image."

  first, if that's true, then it's redundant to incorporate both the
image feature of dev-pkgs *and* the image install of kernel-dev, as is
done in images like core-image-rt-sdk.bb:

IMAGE_FEATURES += "dev-pkgs tools-sdk tools-debug eclipse-debug tools-profile tools-testapps debug-tweaks"

IMAGE_INSTALL += "rt-tests hwlatdetect kernel-dev"

  additionally, the core-image-sato-sdk.bb recipe file is alone in
including:

IMAGE_INSTALL += "kernel-devsrc"

is there a reason that that core-image sdk recipe alone includes
kernel-devsrc while the others do not?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


                 reply	other threads:[~2015-03-02  9:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.11.1503020424530.21001@localhost \
    --to=rpjday@crashcourse.ca \
    --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