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 12:16:33 +0100 [thread overview]
Message-ID: <gkht6i$2b6$1@ger.gmane.org> (raw)
In-Reply-To: <d6d644b80901130305j687168fapb3fa7659f2696742@mail.gmail.com>
On 13-01-09 12:05, Erik Botö wrote:
> Hi,
>
> I'm writing a bitbake recipe for a QT-app that tries to link against
> libQtUiTools but it fails with:
>
> /bin/ld: cannot find -lQtUiTools
>
> I think this is because this file is not in the staging environment
Looking at qt_staging.inc:
for i in libQtAssistantClient${QT_LIBINFIX} \
libQtDesignerComponents${QT_LIBINFIX} \
libQtUiTools${QT_LIBINFIX} \
libQtDesigner${QT_LIBINFIX}
do
sed -i -e "s,-L${libdir},-L${STAGING_LIBDIR},g" $i.prl || true
cp ${STAGE_TEMP}/${libdir}/$i.prl ${STAGING_LIBDIR} || true
sed -i -e
"/^dependency_libs=/s,-L${libdir},-L${STAGING_LIBDIR},g" $i.la || true
cp ${STAGE_TEMP}/${libdir}/$i.la ${STAGING_LIBDIR} || true
oe_libinstall -C ${STAGE_TEMP}/${libdir} -so $i
${STAGING_LIBDIR} || true
oe_libinstall -C ${STAGE_TEMP}/${libdir} -a $i
${STAGING_LIBDIR} || true
done
So it attempts to install to .so (oe_libinstall -so) and the .a
(oe_libinstall -a) to the staging dir.
> (I'm
> using qt-embedded-4.4.3 for building qt).
If you're building qt/e you should link against QtUiTools${QT_LIBINFIX}
(expands to QtUiToolsE in your case), not QtUiTools. AIUI 'inherit
qtopia4core' should take care of all that for you.
regards,
Koen
next prev parent reply other threads:[~2009-01-13 11:23 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 [this message]
2009-01-13 13:27 ` Erik Botö
2009-01-13 13:40 ` 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='gkht6i$2b6$1@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 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.