All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <sgarman@zenlinux.com>
To: openembedded-devel@lists.openembedded.org
Subject: BBCLASSEXTEND sdk vs. nativesdk
Date: Tue, 23 Mar 2010 20:06:13 -0700	[thread overview]
Message-ID: <4BA981A5.5030609@zenlinux.com> (raw)
In-Reply-To: <4B99791E.1020102@zenlinux.com>

Hi all,

I noticed in my attempt to convert zlib to use BBCLASSEXTEND that 
sdk.bbclass has been deprecated, and that the new way is to use 
nativesdk.bbclass. This is confirmed by the fact that the Poky recipe 
for zlib uses:

BBCLASSEXTEND = "native nativesdk"

However, if I use this in the OE recipe, bitbake no longer knows how to 
build zlib-sdk. And zlib-sdk is listed in DEPENDS in a small handful of 
packages.

It seems to me the correct course of action is to use nativesdk in 
BBCLASSEXTEND and rename the dependencies on other recipes, yes?

Thanks,

Scott

-- 
Scott Garman
sgarman at zenlinux dot com



  parent reply	other threads:[~2010-03-24  3:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 23:13 [PATCH/RFC] zlib: convert to BBCLASSEXTEND Scott Garman
2010-03-12  0:18 ` Khem Raj
2010-03-12  3:26   ` Scott Garman
2010-03-12  3:28     ` Scott Garman
2010-03-12 20:39     ` Khem Raj
2010-03-24  3:06 ` Scott Garman [this message]
2010-03-24  5:45   ` BBCLASSEXTEND sdk vs. nativesdk Khem Raj
2010-03-24  6:42     ` Scott Garman
2010-03-24 10:28       ` Richard Purdie
2010-03-24 10:53         ` jkridner
2010-03-24 19:27           ` Denys Dmytriyenko
2010-03-24 15:27         ` Tom Rini
2010-03-24 15:37           ` Richard Purdie
2010-03-24 15:57             ` Tom Rini
2010-03-24 18:05               ` Richard Purdie
2010-03-24 18:46                 ` Tom Rini
2010-03-25 23:11                   ` 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=4BA981A5.5030609@zenlinux.com \
    --to=sgarman@zenlinux.com \
    --cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.