From: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5] Problems with Qt5 and CMake
Date: Mon, 10 Jun 2013 20:32:27 +0200 [thread overview]
Message-ID: <51B61BBB.1030508@herbrechtsmeier.net> (raw)
In-Reply-To: <16136190.1I5tgHWYiU@luxon>
Am 10.06.2013 16:09, schrieb Manuel Nickschas:
> On Friday 24 May 2013 16:56:41 Stefan Herbrechtsmeier wrote:
>> Am 24.05.2013 15:03, schrieb Manuel Nickschas:
>>> The path specified there is clearly wrong for cross-compiling, because it
>>> references the location in the target itself, without prepending the
>>> sysroot prefix. Thus, it won't find moc. In particular, it needs not even
>>> find the moc from the target sysroot, but from the native sysroot, as
>>> it's a host tool.
>> All paths in the target sysroot represents the path on the target. They
>> should be
>> adapted via an variable or automatically detected during runtime.
> What would be the proper way of doing this in the CMake files shipped by
> Qt5?
>
> /usr/bin/qt5/moc is hard-coded. We could prepend that with
> ${STAGING_DIR_NATIVE} maybe, which could be exported (via
> EXTRA_OECMAKE) by recipes so it's picked up by CMake, and it would
> resolve to nothing if it's not set (so the CMake file would still work outside of
> Bitbake).
You can try to import the executable from a file passed via -P parameter
to cmake. I'm not sure if this works.
add_executable(Qt5::rcc IMPORTED)
set_target_properties(Qt5::rcc PROPERTIES IMPORTED_LOCATION
"${STAGING_BINDIR_NATIVE}/rcc4")
Regards,
Stefan
next prev parent reply other threads:[~2013-06-10 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 11:34 [meta-qt5] Problems with Qt5 and CMake Manuel Nickschas
2013-05-24 12:07 ` Martin Jansa
2013-05-24 12:44 ` Stefan Herbrechtsmeier
2013-05-24 13:03 ` Manuel Nickschas
2013-05-24 14:56 ` Stefan Herbrechtsmeier
2013-06-10 14:09 ` Manuel Nickschas
2013-06-10 18:32 ` Stefan Herbrechtsmeier [this message]
2013-06-20 10:06 ` Manuel Nickschas
2013-06-20 11:12 ` Philip Craig
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=51B61BBB.1030508@herbrechtsmeier.net \
--to=stefan@herbrechtsmeier.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox