From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] qt5cinex: depends also on qt5quickcontrols
Date: Thu, 23 Nov 2017 21:45:46 +0100 [thread overview]
Message-ID: <20171123214546.7e982b20@windsurf.lan> (raw)
In-Reply-To: <32a0057b-1840-ef45-c199-9da6b14ae09c@micronovasrl.com>
Hello,
On Tue, 14 Nov 2017 18:03:53 +0100, Giulio Benetti wrote:
> Sorry, my mistake.
> It installed correctly on STAGING_DIR, but not in TARGET_DIR.
> This why it compiled fine, but on target it didn't find that
> libQtQuick.so library.
> This is a problem on building Qt5 I've noticed.
>
> If I build first time Qt5 with few features,
> than select other more features,
> those can be built partially and installed partially too.
>
> To reproduce you can build qt5base.
> After that, select qt5cinex,
> then you should find that libraries are in STAGING_DIR but not in
> TARGET_DIR.
>
> So to have it working properly you have to rm and rebuild qt5base and
> qt5declarative from beginning.
>
> Did someone else noticed this?
So in the end, is your patch needed ?
Peter (Seiderer), could you review this Qt5 related patch ? Thanks!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-23 20:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 16:30 [Buildroot] [PATCH 1/1] qt5cinex: depends also on qt5quickcontrols Giulio Benetti
2017-11-14 16:32 ` Giulio Benetti
2017-11-14 16:58 ` Baruch Siach
2017-11-14 17:03 ` Giulio Benetti
2017-11-14 17:07 ` Baruch Siach
2017-11-14 17:11 ` Giulio Benetti
2017-11-23 20:45 ` Thomas Petazzoni [this message]
2017-11-23 21:19 ` Giulio Benetti
2017-11-23 21:28 ` Peter Seiderer
2017-11-23 21:47 ` Giulio Benetti
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=20171123214546.7e982b20@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.