Skip to contentSkip to conversation

Problem with qmake2 and native sdk

DISCUSSION Philip Balister 2 participants 4 messages Mar 28, 2011

lore
Share & tools
lore
#0 lore raw

I building PyQwt on an omap3 suing the qt native sdk. This leads to the following message:

Could not find mkspecs for your QMAKESPEC(linux-g++) after trying:

        /home/balister/oe/tmp/sysroots/x86_64-linux/qt4/mkspecs

I can work around this by editing the PyQwt configure.py file to use the full path to the linux-g++ spec file, but it would be nice if this worked out of the box.

Does anyone know how to change the default spec file path in qmake2? I've looked at the recipe and nothing jumps out at me to try.

Philip

#1 lore raw

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

Quoted 4 lines · Philip Balister

I building PyQwt on an omap3 suing the qt native sdk. This leads to the following message:

Could not find mkspecs for your QMAKESPEC(linux-g++) after trying:

Quoted 8 lines
        /home/balister/oe/tmp/sysroots/x86_64-linux/qt4/mkspecs

I can work around this by editing the PyQwt configure.py file to use the full path to the linux-g++ spec file, but it would be nice if this worked out of the box.

Does anyone know how to change the default spec file path in qmake2? I've looked at the recipe and nothing jumps out at me to try.

If you are using angstrom, 'opkg install qt4-mkspecs' and source the script that should be in there. That should install the specs and set QMAKE* properly.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNkKJHMkyGM64RGpERAqiCAJ9l1uMOxITkPb+I9P0OckVDIzd/pgCfVclX zkj6vQmqIDwVX4SQF0Uw+7o=
=R3A8
-----END PGP SIGNATURE-----

#2 lore raw
Quoted 14 lines · Koen Kooi

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

Quoted 10 lines · Philip Balister

I building PyQwt on an omap3 suing the qt native sdk. This leads to the following message:

Could not find mkspecs for your QMAKESPEC(linux-g++) after trying:

         /home/balister/oe/tmp/sysroots/x86_64-linux/qt4/mkspecs

I can work around this by editing the PyQwt configure.py file to use the full path to the linux-g++ spec file, but it would be nice if this worked out of the box.

Quoted 6 lines
Quoted 2 lines

Does anyone know how to change the default spec file path in qmake2? I've looked at the recipe and nothing jumps out at me to try.

If you are using angstrom, 'opkg install qt4-mkspecs' and source the script that should be in there. That should install the specs and set QMAKE* properly.

Already done :) I also have an uncommitted patch that adds a var for strip to the environment file. I looked at the env file and didn't see anything to change there either :(

Philip

#3 lore raw

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

Quoted 18 lines · Philip Balister
Quoted 17 lines · Koen Kooi

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

Quoted 12 lines · Philip Balister

I building PyQwt on an omap3 suing the qt native sdk. This leads to the following message:

Could not find mkspecs for your QMAKESPEC(linux-g++) after trying:

         /home/balister/oe/tmp/sysroots/x86_64-linux/qt4/mkspecs

I can work around this by editing the PyQwt configure.py file to use the full path to the linux-g++ spec file, but it would be nice if this worked out of the box.

Does anyone know how to change the default spec file path in qmake2? I've looked at the recipe and nothing jumps out at me to try.

Quoted 7 lines
Quoted 3 lines

If you are using angstrom, 'opkg install qt4-mkspecs' and source the script that should be in there. That should install the specs and set QMAKE* properly.

Already done :) I also have an uncommitted patch that adds a var for strip to the environment file. I looked at the env file and didn't see anything to change there either :(

In that case the OE patch to make qmake honour env vars might have gotten lost. Can you compare the 4.6.x and 4.7.x patches? -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNkNpEMkyGM64RGpERAk63AKCBAhqhScCvx9z/sF7U5qGoEhqe+ACgleh5 o1zMQiFCvov11hvc10K/s8Q=
=JeQb
-----END PGP SIGNATURE-----