Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-commits@openembedded.org
Subject: Re: [oe-commits] Koen Kooi : qt4: add 4.6.2
Date: Wed, 17 Feb 2010 11:48:16 +0100	[thread overview]
Message-ID: <20100217104816.GJ3233@jama> (raw)
In-Reply-To: <E1Nhfko-0005L8-Mc@melo.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

On Wed, Feb 17, 2010 at 08:59:30AM +0000, git version control wrote:
> Module: openembedded.git
> Branch: org.openembedded.dev
> Commit: fba63ed00f92f939529bd1fd1f47a8d715f8bea8
> URL:    http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=fba63ed00f92f939529bd1fd1f47a8d715f8bea8
> 
> Author: Koen Kooi <koen@openembedded.org>
> Date:   Tue Feb 16 10:47:02 2010 +0100
> 
> qt4: add 4.6.2
> 
> * fix 4.6.1 references in 4.6.0 files as well
> * make qt-config.patch work with QT_NO_CAST_{TO,FROM},ASCII strict checking

No idea if that's new issue with 4.6.2 or because of my chroot, but now
it cannot find any headers from staging.

I found that now there is LFLAGS (not LDFLAGS) set with libdir and patched 
configure to use that too somehow, maybe it was needed before -I -L parameters
added to configure script itself?

Attached patch works for me.. but if it's right way, then it should be
integrated to .inc files instead.

Regards,

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa                         

[-- Attachment #2: 0001-qt4-tools-native-use-I-and-L-to-specify-staging-dire.patch --]
[-- Type: text/plain, Size: 999 bytes --]

From d86a53dc732810f3a0ed93664cb1bad03177bdb4 Mon Sep 17 00:00:00 2001
From: Martin Jansa <Martin.Jansa@gmail.com>
Date: Wed, 17 Feb 2010 11:39:34 +0100
Subject: [PATCH] qt4-tools-native: use -I and -L to specify staging directories

---
 recipes/qt4/qt4-tools-native_4.6.2.bb |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/recipes/qt4/qt4-tools-native_4.6.2.bb b/recipes/qt4/qt4-tools-native_4.6.2.bb
index d9ab033..c40738b 100644
--- a/recipes/qt4/qt4-tools-native_4.6.2.bb
+++ b/recipes/qt4/qt4-tools-native_4.6.2.bb
@@ -13,6 +13,8 @@ SRC_URI = "ftp://ftp.trolltech.com/qt/source/qt-everywhere-opensource-src-${PV}.
 S = "${WORKDIR}/qt-everywhere-opensource-src-${PV}"
 
 EXTRA_OECONF = "-prefix ${prefix} \
+                -L ${STAGING_LIBDIR_NATIVE} \
+                -I ${STAGING_INCDIR_NATIVE} \
                 -qt-libjpeg -qt-gif -system-zlib \
                 -no-libjpeg -no-libpng \
                 -no-accessibility \
-- 
1.7.0


       reply	other threads:[~2010-02-17 10:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Nhfko-0005L8-Mc@melo.openembedded.org>
2010-02-17 10:48 ` Martin Jansa [this message]
2010-02-17 11:32   ` Koen Kooi : qt4: add 4.6.2 Koen Kooi
2010-02-17 19:46     ` Holger Hans Peter Freyther
2010-02-17 19:53       ` Koen Kooi
2010-02-18  8:49         ` Martin Jansa
2010-02-18 10:20         ` Martin Jansa
2010-02-18 11:01           ` Koen Kooi

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=20100217104816.GJ3233@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-commits@openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox