Re: Dropping qtopia-core-4.3.3.bb and qtopia4core.bbclass

["Jeremy Lainé" <jeremy.laine@bolloretelecom.eu>]

-----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-----