From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Missing includes in STAGING_INCDIR
Date: Tue, 4 Mar 2008 12:47:39 +0100 [thread overview]
Message-ID: <200803041247.39758.mickey@vanille-media.de> (raw)
In-Reply-To: <200803041240.17891.thomas.cooksey@trolltech.com>
Hi Tom,
On Tuesday 04 March 2008 12:40:17 Tom Cooksey wrote:
> I am writing a recipie for Qt/Embedded 4.4 beta (using qt4 recipies as a
> base). At the moment Qt's configure test fails on dbus. I have added
> -I${STAGING_INCDIR}/dbus-1.0 to the configure flags so the configure test
> now picks up dbus/dbus.h correctly.
>
> However, dbus.h itself includes dbus/dbus-arch-deps.h, which is not in
> ${STAGING_INCDIR}/dbus-1.0/*, but _is_ in the dbus work dir. This means I
> have to add the dbus work dir to the include list, which feels wrong.
Surely that's wrong. Actually dbus-arch-deps.h is where it belongs to,
${libdir}/dbus-1.0/include/. On my favourite system this is:
tmp/staging/arm-angstrom-linux-gnueabi/lib/dbus-1.0/include/dbus/dbus-arch-deps.h
> I have had the same problem with gstreamer too. I think something has
> broken recently, as I've tried building the existing qtopia core recipies
> and had the same failures.
Just rely on pkgconfig and it will do the job. The relevant excerpt for dbus
is:
Name: dbus
Description: Free desktop message bus
Version: 1.1.20
Libs: -L${libdir} -ldbus-1
Cflags: -I${includedir}/dbus-1.0 -I${libdir}/dbus-1.0/include
:M:
--
Dr. Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de
next prev parent reply other threads:[~2008-03-04 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 11:40 Missing includes in STAGING_INCDIR Tom Cooksey
2008-03-04 11:47 ` Michael 'Mickey' Lauer [this message]
2008-03-04 12:20 ` Tom Cooksey
2008-03-04 12:25 ` Michael 'Mickey' Lauer
2008-03-04 12:56 ` Tom Cooksey
2008-03-04 16:05 ` Richard Purdie
2008-03-04 16:29 ` Tom Cooksey
2008-03-04 16:40 ` 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=200803041247.39758.mickey@vanille-media.de \
--to=mickey@vanille-media.de \
--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.