All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Problem with qmake2 and native sdk
Date: Mon, 28 Mar 2011 11:05:30 -0400	[thread overview]
Message-ID: <4D90A3BA.6000609@balister.org> (raw)
In-Reply-To: <imq7o7$sa6$1@dough.gmane.org>

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



  reply	other threads:[~2011-03-28 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2011-03-28 18:58     ` 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=4D90A3BA.6000609@balister.org \
    --to=philip@balister.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 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.