From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] gtk+: define empty PACKAGES_DYNAMIC_virtclass-native
Date: Thu, 17 Mar 2011 13:41:19 +0000 [thread overview]
Message-ID: <1300369279.9054.3.camel@phil-desktop> (raw)
In-Reply-To: <20110317125759.GA3585@jama.jama.net>
On Thu, 2011-03-17 at 13:57 +0100, Martin Jansa wrote:
> On Thu, Mar 17, 2011 at 12:29:39PM +0000, Phil Blundell wrote:
> > On Thu, 2011-03-17 at 13:08 +0100, Martin Jansa wrote:
> > > --- a/recipes/gtk+/gtk+_2.18.6.bb
> > > +++ b/recipes/gtk+/gtk+_2.18.6.bb
> > > @@ -19,6 +19,7 @@ EXTRA_OECONF = "--with-libtiff ${XKBTOGGLE} --disable-glibtest gio_can_sniff=yes
> > > EXTRA_OECONF_append_virtclass-native = " --without-libtiff --without-libjpeg --disable-cups"
> > >
> > > PACKAGES_DYNAMIC = "gtk-module-* gdk-pixbuf-loader-* gtk-immodule-* gtk-printbackend-*"
> > > +PACKAGES_DYNAMIC_virtclass-native = ""
> >
> > Can you not put this in gtk+.inc?
>
> Not all 13 versions we have are including gtk+.inc. But after rechecking
> I could put it only to 4 recipes (I'll resend smaller patch).
>
> bitbake@jama ~/dev/recipes/gtk+ $ git grep BBCLASSEXTEND
> gtk+_2.14.2.bb:BBCLASSEXTEND = "native"
> gtk+_2.18.6.bb:BBCLASSEXTEND = "native"
> gtk+_2.20.0.bb:BBCLASSEXTEND = "native"
> gtk+_2.20.1.bb:BBCLASSEXTEND = "native"
>
> and let the older versions die with migration to meta-oe or let
> someone who cares about gtk to remove them completely.
The four versions you mentioned there do all include gtk+.inc (only the
very old ones like 2.6 don't). So you can put it there and make an even
smaller patch with the same effect.
p.
prev parent reply other threads:[~2011-03-17 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 12:08 [PATCH] gtk+: define empty PACKAGES_DYNAMIC_virtclass-native Martin Jansa
2011-03-17 12:29 ` Phil Blundell
2011-03-17 12:57 ` Martin Jansa
2011-03-17 13:03 ` [PATCHv2] gtk+: define empty PACKAGES_DYNAMIC_virtclass-native in recipes with native BBCLASSEXTEND Martin Jansa
2011-03-17 13:41 ` Phil Blundell [this message]
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=1300369279.9054.3.camel@phil-desktop \
--to=philb@gnu.org \
--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.