Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Scott Garman <sgarman@zenlinux.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH/RFC] zlib: convert to BBCLASSEXTEND
Date: Thu, 11 Mar 2010 19:28:46 -0800	[thread overview]
Message-ID: <4B99B4EE.5020304@zenlinux.com> (raw)
In-Reply-To: <4B99B467.2090807@zenlinux.com>

[-- Attachment #1: Type: text/plain, Size: 378 bytes --]

On 03/11/2010 07:26 PM, Scott Garman wrote:
> Gotcha, thanks for the feedback. Let's try this then. In the future I
> assume the format-patch email should be sent directly to the list and
> not as an attachment - correct me if I'm mistaken.

...and it would be helpful if I actually included the patch this time.

Scott

-- 
Scott Garman
sgarman at zenlinux dot com

[-- Attachment #2: 0001-zlib-convert-to-new-style-staging-and-BBCLASSEXTEND.patch --]
[-- Type: text/x-patch, Size: 1658 bytes --]

From 322589252447f6bb4a96b79b5495001f6cb64f12 Mon Sep 17 00:00:00 2001
From: Scott Garman <sgarman@zenlinux.com>
Date: Thu, 11 Mar 2010 19:15:29 -0800
Subject: [PATCH] zlib: convert to new style staging and BBCLASSEXTEND

---
 recipes/zlib/zlib-native_1.2.3.bb |    5 -----
 recipes/zlib/zlib-sdk_1.2.3.bb    |    4 ----
 recipes/zlib/zlib_1.2.3.bb        |    6 ++----
 3 files changed, 2 insertions(+), 13 deletions(-)
 delete mode 100644 recipes/zlib/zlib-native_1.2.3.bb
 delete mode 100644 recipes/zlib/zlib-sdk_1.2.3.bb

diff --git a/recipes/zlib/zlib-native_1.2.3.bb b/recipes/zlib/zlib-native_1.2.3.bb
deleted file mode 100644
index d7e0777..0000000
--- a/recipes/zlib/zlib-native_1.2.3.bb
+++ /dev/null
@@ -1,5 +0,0 @@
-require zlib_${PV}.bb
-ZLIB_EXTRA = ""
-DEPENDS = "libtool-native"
-
-inherit native
diff --git a/recipes/zlib/zlib-sdk_1.2.3.bb b/recipes/zlib/zlib-sdk_1.2.3.bb
deleted file mode 100644
index 4863395..0000000
--- a/recipes/zlib/zlib-sdk_1.2.3.bb
+++ /dev/null
@@ -1,4 +0,0 @@
-require zlib_${PV}.bb
-LIB_EXTRA = ""
-
-inherit sdk
diff --git a/recipes/zlib/zlib_1.2.3.bb b/recipes/zlib/zlib_1.2.3.bb
index d995869..db4b16b 100644
--- a/recipes/zlib/zlib_1.2.3.bb
+++ b/recipes/zlib/zlib_1.2.3.bb
@@ -3,7 +3,7 @@ SECTION = "libs"
 PRIORITY = "required"
 HOMEPAGE = "http://www.gzip.org/zlib/"
 LICENSE = "zlib"
-PR ="r5"
+PR ="r6"
 
 SRC_URI = "http://www.zlib.net/zlib-1.2.3.tar.bz2 \
 		file://visibility.patch;patch=1 \
@@ -15,6 +15,4 @@ DEPENDS = "libtool-cross"
 
 inherit autotools
 
-do_stage() {
-	autotools_stage_all
-}
+BBCLASSEXTEND = "native sdk"
-- 
1.6.3.3


  reply	other threads:[~2010-03-12  3:31 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 [this message]
2010-03-12 20:39     ` Khem Raj
2010-03-24  3:06 ` BBCLASSEXTEND sdk vs. nativesdk Scott Garman
2010-03-24  5:45   ` 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=4B99B4EE.5020304@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox