From: Peter <ppf83764@freenet.de>
To: Jonathan Liu <net147@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5] How to build Qt5 with 'designer' module?
Date: Thu, 16 Oct 2014 13:55:17 +0200 [thread overview]
Message-ID: <543FB225.8020304@freenet.de> (raw)
In-Reply-To: <543F91D1.9070707@gmail.com>
Hi Jonathan,
On 10/16/2014 11:37 AM, Jonathan Liu wrote:
> Hi Peter,
>
> On 15/10/2014 11:47 PM, Peter wrote:
>> Hi Jonathan,
>>
>> thanks for the reply.
>>
>> On 13 Oktober 2014 04:30, Jonathan Liu <net147@gmail.com> wrote:
>>
>>> Hi Peter,
>>>
>>> On 9 October 2014 18:13, Fink, Peter <pfink@christ-elektronik.de> wrote:
>>>> I’m trying to build a Qt application with the toolchain generated by
>>>> openembedded (meta-toolchain-qt5).
>>>>
>>>> The application needs the designer-module, which I thought was
>>>> included in the qttools package, but now I get the following error:
>>>>
>>>> “Project Error: Unknown module(s) in QT: designer.”
>>>>
>>>> What do I have to include to get the designer module?
>>>>
>>>> Another thing I run into was the missing syncqt.pl script in the
>>>> toolchain as I need qftp. A link syncqt -> syncqt.pl was present.
>>>> Is it missing by accident or for a reason?
>>>>
>>>> I was using Qt. 5.3.1 02861e677ab....
>>> You can try backporting the following patches:
>>> http://patchwork.openembedded.org/patch/81599/
>>> http://patchwork.openembedded.org/patch/81603/
>>
>> I tried your patches. syncqt.pl is included now, but my application
>> still did not compile.
>> I had to remove qttools-plugins, because it gave me a "cannot install
>> qttools-plugins" error while generating the toolchain - maybe this was
>> the reason why the libs were not included?
>> Now I tested hacking it into qtbase.inc and it seems to include the
>> qtdesigner libs:
>>
>> @@ -131,6 +132,7 @@ QT_CONFIG_FLAGS += " \
>> -no-pch \
>> -no-rpath \
>> -pkg-config \
>> + -make tools \
>> ${EXTRA_OECONF} \
>> "
>>
>> Regards,
>> Peter
>>
> Make sure you have "tools" in PACKAGECONFIG for qtbase if you are
> overriding PACKAGECONFIG as this will add "-make tools" to QT_CONFIG_FLAGS.
> What do you have PACKAGECONFIG set to for the qtbase recipe?
>
> Regards,
> Jonathan
I thought these lines include the 'tools' PACKAGECONFIG:
qtbase.inc:
...
PACKAGECONFIG[tools] = "-make tools,-nomake tools"
...
PACKAGECONFIG_DEFAULT ?= "dbus udev evdev widgets tools libs"
PACKAGECONFIG ?= " \
${PACKAGECONFIG_RELEASE} \
${PACKAGECONFIG_DEFAULT} \
${PACKAGECONFIG_OPENSSL} \
${PACKAGECONFIG_GL} \
${PACKAGECONFIG_FB} \
${PACKAGECONFIG_X11} \
${PACKAGECONFIG_FONTS} \
${PACKAGECONFIG_SYSTEM} \
${PACKAGECONFIG_MULTIMEDIA} \
${PACKAGECONFIG_DISTRO} \
"
But maybe the PACKAGECONFIG is overridden somewhere and I missed it or I
got the whole PACKAGECONFIG thing wrong. Is there a possibility to check
the actually used PACKAGECONFIG or the qt5 configure command altogether?
Regards,
Peter
next prev parent reply other threads:[~2014-10-16 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 7:13 [meta-qt5] How to build Qt5 with 'designer' module? Fink, Peter
2014-10-13 2:30 ` Jonathan Liu
[not found] ` <F50ED7964AF8784493DDA71A307917F90E435CF2@BEXBE01.christ.local>
2014-10-15 12:47 ` Peter
2014-10-16 9:37 ` Jonathan Liu
2014-10-16 11:55 ` Peter [this message]
2014-10-16 12:05 ` Jonathan Liu
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=543FB225.8020304@freenet.de \
--to=ppf83764@freenet.de \
--cc=net147@gmail.com \
--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