From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] qt4-tools-nativesdk: fix unpack failure due to missing g++.conf
Date: Tue, 21 Jun 2011 08:37:47 +0100 [thread overview]
Message-ID: <201106210837.47377.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <4DFFDE40.2040306@gmail.com>
On Tuesday 21 June 2011 00:56:48 Khem Raj wrote:
> On 06/18/2011 11:56 AM, Paul Eggleton wrote:
> > FILESPATHPKG was being used to in order to bring in linux.conf and
> > g++.conf in this recipe, however this probably never worked since
> > FILESPATHPKG always has the MACHINE appended to it and these are not
> > machine-specific files.
>
> FILESPATHPKG is not supported in oe-core. Its an oe.dev feature for now.
Right, but there's still a reference to it in utils.bbclass where it
supposedly operates in the manner I described. This patch actually removes its
usage in the qt4-tools-nativesdk recipe however.
Cheers,
Paull
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-21 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 18:56 [PATCH 0/3] qt4-tools-nativesdk fixes Paul Eggleton
2011-06-18 18:56 ` [PATCH 1/3] qt4-tools-nativesdk: fix unpack failure due to missing g++.conf Paul Eggleton
2011-06-20 23:56 ` Khem Raj
2011-06-21 7:37 ` Paul Eggleton [this message]
2011-06-18 18:56 ` [PATCH 2/3] qt4-tools-nativesdk: drop freetype include as we build with -no-freetype Paul Eggleton
2011-06-18 18:56 ` [PATCH 3/3] qt4-tools-nativesdk: fix compile failure in src/dbus Paul Eggleton
2011-06-22 16:42 ` [PATCH 0/3] qt4-tools-nativesdk fixes 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=201106210837.47377.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@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