From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] QtSerialPort: new package
Date: Tue, 06 Nov 2012 01:49:46 +0100 [thread overview]
Message-ID: <50985EAA.9000009@mind.be> (raw)
In-Reply-To: <CAExDhvZaPz1pJSdrY1hWAMXV15Wp6LAtJb6y0Qbpn26YQtYQoQ@mail.gmail.com>
On 11/05/12 14:37, Thiago A. Corr?a wrote:
>> > Thiago> +define QTSERIALPORT_INSTALL_STAGING_CMDS
>> > Thiago> + $(MAKE) -C $(@D)/src install
>> > Thiago> + mv $(HOST_DIR)/usr/include/QtAddOnSerialPort $(STAGING_DIR)/usr/include/
>> >
>> > That seems funky. Why is it installing under HOST_DIR in the first
>> > place?
> Beats me:(
> The makefile generated by qmake is installing them there. Haven't
> found a better way to fix that so far.
Yikes!
./host/usr/bin/qmake -query
QT_INSTALL_PREFIX:/home/arnout/src/buildroot/output/host/usr
QT_INSTALL_DATA:/home/arnout/src/buildroot/output/host/usr
QT_INSTALL_DOCS:/home/arnout/src/buildroot/output/host/usr/doc
QT_INSTALL_HEADERS:/home/arnout/src/buildroot/output/host/usr/x86_64-buildroot-linux-gnu/sysroot/usr/include
QT_INSTALL_LIBS:/home/arnout/src/buildroot/output/host/usr/x86_64-buildroot-linux-gnu/sysroot/usr/lib
QT_INSTALL_BINS:/home/arnout/src/buildroot/output/host/usr/bin
QT_INSTALL_PLUGINS:/home/arnout/src/buildroot/output/host/usr/plugins
QT_INSTALL_IMPORTS:/home/arnout/src/buildroot/output/host/usr/imports
QT_INSTALL_TRANSLATIONS:/home/arnout/src/buildroot/output/host/usr/translations
QT_INSTALL_CONFIGURATION:/home/arnout/src/buildroot/output/host/usr
QT_INSTALL_EXAMPLES:/home/arnout/src/buildroot/output/host/usr
QT_INSTALL_DEMOS:/home/arnout/src/buildroot/output/host/usr
QMAKE_MKSPECS:/home/arnout/src/buildroot/output/host/usr/mkspecs
QMAKE_VERSION:2.01a
QT_VERSION:4.8.3
This is because we install qmake in $(HOST_DIR) and use a qt.conf to make
the paths point back to staging, but only for headers and libraries. Thomas,
do you remember why you didn't do that for prefix and data? (qt.mk:569-573,
introduced by ca290e7e).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2012-11-06 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 15:49 [Buildroot] [PATCHv3] QtSerialPort: new package Thiago A. Correa
2012-11-03 16:46 ` Peter Korsgaard
2012-11-03 17:21 ` Yegor Yefremov
2012-11-03 18:17 ` Peter Korsgaard
2012-11-05 13:37 ` Thiago A. Corrêa
2012-11-06 0:49 ` Arnout Vandecappelle [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=50985EAA.9000009@mind.be \
--to=arnout@mind.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox