From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Qt-app won't build since libQtUiTools not included in staging
Date: Tue, 13 Jan 2009 14:40:18 +0100 [thread overview]
Message-ID: <gki5k2$jm$2@ger.gmane.org> (raw)
In-Reply-To: <d6d644b80901130527x62dca925wfff7c91e14a4671f@mail.gmail.com>
On 13-01-09 14:27, Erik Botö wrote:
> Hi again!
>
> When I build qt-embedded I get the "E" suffix on all libraries but
> QtUiTools. If I enter the workdir for qt-embedded and lists the content of
> the lib-dir I have all the .la libraries with the E suffix, like
> "libQtGuiE.la" etc. But the QtUiTools file is called "libQtUiTools.a"
> without the "E". So if qt_staging.inc expects the suffix to be there I guess
> it won't find the file?
>
> Is the QtUiTools some kind of exception, or should it also be suffixed with
> an E?
I would class it as a bug and make the QT people look at it, Holger?
regards,
Koen
prev parent reply other threads:[~2009-01-13 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 11:05 Qt-app won't build since libQtUiTools not included in staging Erik Botö
2009-01-13 11:16 ` Koen Kooi
2009-01-13 13:27 ` Erik Botö
2009-01-13 13:40 ` Koen Kooi [this message]
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='gki5k2$jm$2@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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