* Problem with qmake2 and native sdk
@ 2011-03-28 14:29 Philip Balister
2011-03-28 14:59 ` Koen Kooi
0 siblings, 1 reply; 4+ messages in thread
From: Philip Balister @ 2011-03-28 14:29 UTC (permalink / raw)
To: openembedded-devel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Problem with qmake2 and native sdk
2011-03-28 14:29 Problem with qmake2 and native sdk Philip Balister
@ 2011-03-28 14:59 ` Koen Kooi
2011-03-28 15:05 ` Philip Balister
0 siblings, 1 reply; 4+ messages in thread
From: Koen Kooi @ 2011-03-28 14:59 UTC (permalink / raw)
To: openembedded-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 28-03-11 16:29, Philip Balister wrote:
> 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.
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-----
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Problem with qmake2 and native sdk
2011-03-28 14:59 ` Koen Kooi
@ 2011-03-28 15:05 ` Philip Balister
2011-03-28 18:58 ` Koen Kooi
0 siblings, 1 reply; 4+ messages in thread
From: Philip Balister @ 2011-03-28 15:05 UTC (permalink / raw)
To: openembedded-devel
On 03/28/2011 10:59 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 28-03-11 16:29, Philip Balister wrote:
>> 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.
>
> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Problem with qmake2 and native sdk
2011-03-28 15:05 ` Philip Balister
@ 2011-03-28 18:58 ` Koen Kooi
0 siblings, 0 replies; 4+ messages in thread
From: Koen Kooi @ 2011-03-28 18:58 UTC (permalink / raw)
To: openembedded-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 28-03-11 17:05, Philip Balister wrote:
> On 03/28/2011 10:59 AM, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 28-03-11 16:29, Philip Balister wrote:
>>> 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.
>>
>> 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-----
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-03-28 19:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-28 14:29 Problem with qmake2 and native sdk Philip Balister
2011-03-28 14:59 ` Koen Kooi
2011-03-28 15:05 ` Philip Balister
2011-03-28 18:58 ` Koen Kooi
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.