From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH v2] gupnp_0.13.4/gupnp-av_0.5.9: disable introspection
Date: Mon, 7 Mar 2011 10:59:37 -0700 [thread overview]
Message-ID: <4D751D09.6000808@mentor.com> (raw)
In-Reply-To: <1299517044.2132.203.camel@phil-desktop>
On 03/07/2011 09:57 AM, Phil Blundell wrote:
> On Mon, 2011-03-07 at 17:43 +0100, Steffen Sledz wrote:
>> --- a/recipes/upnp/gupnp_0.13.4.bb
>> +++ b/recipes/upnp/gupnp_0.13.4.bb
>> @@ -2,13 +2,14 @@ LICENSE = "LGPL"
>> DEPENDS = "e2fsprogs gssdp libsoup-2.4 libxml2 gtk-doc-native libgee"
>>
>> require gupnp.inc
>> +PR = "1"
"r1"
>>
>> SRC_URI[md5sum] = "0d562f5f02534c70c3743b2c514db8ba"
>> SRC_URI[sha256sum] = "7974953f38a41236c875c3df509abc43e8218b5925fdc18212a73b1ae0d0e7e8"
>>
>> inherit autotools pkgconfig
>>
>> -EXTRA_OECONF = "--disable-gtk-doc"
>> +EXTRA_OECONF = "--disable-gtk-doc --enable-introspection=no"
>
> I can't help thinking that there must be a better place to put this,
> maybe even autotools.bbclass. We basically want those options for all
> packages that will take them, right?
Usually this is just in "gnome" stuff and gnome or gnomebase does handle
this. But indeed, perhaps this is something that should be more widely
passed in to avoid semi-random breakage.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-03-07 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 14:31 Release-2011.03 gupnp-0.13.4-r0: task do_compile: Failed Steffen Sledz
2011-03-07 8:51 ` Steffen Sledz
2011-03-07 10:47 ` Steffen Sledz
2011-03-07 14:35 ` Tom Rini
2011-03-07 16:28 ` [PATCH] gupnp_0.13.4: disable introspection Steffen Sledz
2011-03-07 16:43 ` [PATCH v2] gupnp_0.13.4/gupnp-av_0.5.9: " Steffen Sledz
2011-03-07 16:57 ` Phil Blundell
2011-03-07 17:59 ` Tom Rini [this message]
2011-03-08 11:49 ` Steffen Sledz
2011-03-08 12:12 ` Koen Kooi
2011-03-08 12:56 ` Steffen Sledz
2011-03-08 13:39 ` Steffen Sledz
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=4D751D09.6000808@mentor.com \
--to=tom_rini@mentor.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.