From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 7/8] gobject-introspection.bbclass: make additional DEPENDS conditional
Date: Thu, 17 Mar 2016 22:16:07 +0000 [thread overview]
Message-ID: <1458252967.7615.36.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160317213608.GG2553@jama>
On Thu, 2016-03-17 at 22:36 +0100, Martin Jansa wrote:
> On Thu, Mar 17, 2016 at 05:29:59PM +0000, Burton, Ross wrote:
> > On 17 March 2016 at 17:19, Andre McCurdy <armccurdy@gmail.com>
> > wrote:
> >
> > > # Generating introspection data depends on a combination of
> > > native and
> > > target
> > > # introspection tools, and qemu to run the target tools.
> > > -DEPENDS_append = " gobject-introspection gobject-introspection
> > > -native
> > > qemu-native"
> > > +DEPENDS_append = " ${@bb.utils.contains('COMBINED_FEATURES',
> > > 'gobject-introspection-data', 'gobject-introspection
> > > gobject-introspection-native qemu-native', '', d)}"
> > >
> >
> > Have you verified this works with g-i disabled and a clean sysroot?
> > I'm
> > thinking builds will still need at least some of this to provide
> > the m4
> > macros.
>
> Even with gobject-introspection-data removed from DISTRO_FEATURES I'm
> seeing
> couple recipes (our version of gst-*) failing with:
>
> > configure:22282: error: possibly undefined macro:
> > PKG_CONFIG_SYSROOT_DIR
> > If this token and others are legitimate, please use
> > m4_pattern_allow.
> > See the Autoconf documentation.
>
> and PKG_CONFIG_SYSROOT_DIR is added by introspection.m4 from g-i
> patchset.
Sounds like a missing pkgconfig depends somewhere. Does the g-i class
inherit pkgconfig?
Cheers,
Richard
next prev parent reply other threads:[~2016-03-17 22:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 17:19 [PATCH 0/8] gobject introspection fixes Andre McCurdy
2016-03-17 17:19 ` [PATCH 1/8] bitbake.conf: remove 'gobject-introspection-data' from DISTRO/MACHINE_FEATURES_BACKFILL Andre McCurdy
2016-03-17 17:31 ` Burton, Ross
2016-03-17 18:17 ` Andre McCurdy
2016-03-17 21:02 ` Richard Purdie
2016-03-18 11:08 ` Andre McCurdy
2016-03-21 14:15 ` Alexander Kanavin
2016-03-21 16:31 ` Richard Purdie
2016-03-17 17:19 ` [PATCH 2/8] default-distrovars.inc: add gobject-introspection-data to DISTRO_FEATURES_DEFAULT Andre McCurdy
2016-03-17 17:19 ` [PATCH 3/8] qemu.inc: add gobject-introspection-data to MACHINE_FEATURES Andre McCurdy
2016-03-17 17:19 ` [PATCH 4/8] arch-x86.inc: disable gobject introspection for x86-64 x32 builds Andre McCurdy
2016-03-17 17:19 ` [PATCH 5/8] qemuarm64.conf: don't clear MACHINE_FEATURES Andre McCurdy
2016-03-17 17:19 ` [PATCH 6/8] gobject-introspection.bbclass: wrap comments at 80 columns Andre McCurdy
2016-03-17 17:19 ` [PATCH 7/8] gobject-introspection.bbclass: make additional DEPENDS conditional Andre McCurdy
2016-03-17 17:29 ` Burton, Ross
2016-03-17 17:44 ` Andre McCurdy
2016-03-17 21:36 ` Martin Jansa
2016-03-17 22:16 ` Richard Purdie [this message]
2016-03-18 19:22 ` alexander.kanavin
2016-03-18 20:46 ` Martin Jansa
2016-03-17 17:19 ` [PATCH 8/8] gobject-introspection.bbclass: mark as machine specific due to COMBINED_FEATURES Andre McCurdy
2016-03-17 17:29 ` Martin Jansa
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=1458252967.7615.36.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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