Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Jeremy Lainé" <jeremy.laine@bolloretelecom.eu>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Dropping qtopia-core-4.3.3.bb and qtopia4core.bbclass
Date: Wed, 18 Mar 2009 15:40:35 +0100	[thread overview]
Message-ID: <49C107E3.30505@bolloretelecom.eu> (raw)
In-Reply-To: <20090317171705.208a7d31@kmfms>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jim,

> Now if I "inherit qt4e" they fail with something like this:
>
> | NOTE: using qmake spec in
> /home/jim/Projects/gumstix/oe/tmp/cross/armv7a/share/qt4/mkspecs/linux-gnueabi-oe-g++,
>  using profiles '' | NOTE: qmake prevar substitution:
> QT_LIBINFIX=E | Failure to read QMAKESPEC conf file
> /home/jim/Projects/gumstix/oe/tmp/cross/armv7a/share/qt4/mkspecs/linux-gnueabi-oe-g++/qmake.conf.
>  | Error processing project file: flickcharm.pro | FATAL: Error
> calling
> /home/jim/Projects/gumstix/oe/tmp/staging/i686-linux/usr/bin/qmake2
>  on flickcharm.pro
>
> Is tmp/cross/armv7a/share/qt4/mkspecs/linux-gnueabi-oe-g++ the
> correct path?  I have a
> tmp/cross/i686/share/qt4/mkspecs/linux-gnueabi-oe-g++ area, but not
> tmp/cross/armv7a/share/qt4/mkspecs/linux-gnueabi-oe-g++.
>
> I'm assuming I just need to do something more than just "inherit
> qt4e" in my recipe?  Perhaps I'm seeing a bug specific to the
> gumstix branch?

To my knowledge qmake support has been busted for a while (I also have
your problem if I try to build a qmake-based package), I'm suprised
this hasn't cropped up earlier.

I'll try to look into it, but I don't quite understand the way
"qmake2-native" is packaged (why is it a "cross" package?), and where
the "mkspecs" directories end up.

If someone can help shed some light on this, I'm all ears!

- --
Jeremy LAINE
Bolloré telecom | 11bis, rue Scribe | F-75009 Paris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknBB+IACgkQCL1n3lVB9Ea2AQCgvutQjRjjeriH5++gUWi/1whr
3FQAn0Vn2CQEhW9ZESouNaxglZucqsOQ
=PAED
-----END PGP SIGNATURE-----




  reply	other threads:[~2009-03-18 14:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 13:22 Dropping qtopia-core-4.3.3.bb and qtopia4core.bbclass Jeremy Lainé
2009-03-17 13:35 ` Michael 'Mickey' Lauer
2009-03-17 14:03   ` Jeremy Lainé
2009-03-17 21:17     ` Jim Sheldon
2009-03-18 14:40       ` Jeremy Lainé [this message]
2009-03-18 15:29         ` Michael 'Mickey' Lauer
2009-03-18 15:49         ` Koen Kooi
2009-03-20 17:26           ` Aloisio Almeida
2009-03-23  4:12             ` Otavio Salvador
2009-03-24 11:56             ` Jeremy Lainé
2009-03-24 13:11               ` Holger Schurig
2009-03-24 19:57       ` Jeremy Lainé
2009-03-24 22:04         ` Jim Sheldon

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=49C107E3.30505@bolloretelecom.eu \
    --to=jeremy.laine@bolloretelecom.eu \
    --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