From: "Fatih Aşıcı" <fatih.asici@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] qt5base: use ccache if enabled
Date: Fri, 29 Nov 2013 09:10:54 +0200 [thread overview]
Message-ID: <201311290910.54807.fatih.asici@gmail.com> (raw)
In-Reply-To: <87eh60xjl4.fsf@dell.be.48ers.dk>
On Friday 29 November 2013 00:11:35 Peter Korsgaard wrote:
> > --- /dev/null
> > +++ b/mkspecs/devices/linux-buildroot-g++/qmake.conf
> >
> > -@@ -0,0 +1,11 @@
> > +@@ -0,0 +1,15 @@
> >
> > +include(../common/linux_device_pre.conf)
> > +
> >
> > ++# modifications to g++.conf
> > ++QMAKE_CC = $${BUILDROOT_CCACHE} $${QMAKE_CC}
> > ++QMAKE_CXX = $${BUILDROOT_CCACHE} $${QMAKE_CXX}
> > ++
> >
> > +#modifications to gcc-base.conf
> > +QMAKE_CFLAGS += $${BUILDROOT_COMPILER_CFLAGS}
> > +QMAKE_CXXFLAGS += $${BUILDROOT_COMPILER_CXXFLAGS}
> >
> > diff --git a/package/qt5/qt5base/qt5base.mk
> > b/package/qt5/qt5base/qt5base.mk index febdc9b..a1d5dba 100644
> > --- a/package/qt5/qt5base/qt5base.mk
> > +++ b/package/qt5/qt5base/qt5base.mk
> > @@ -168,6 +168,7 @@ define QT5BASE_CONFIGURE_CMDS
> >
> > -nomake examples -nomake tests \
> > -device buildroot \
> > -device-option CROSS_COMPILE="$(TARGET_CROSS)" \
> >
> > + -device-option BUILDROOT_CCACHE="$(CCACHE)" \
>
> Can't we just pass it in CROSS_COMPILE?
No. linux_device_pre.conf uses CROSS_COMPILE for other tools, too (ar,
objcopy, ...).
# modifications to g++-unix.conf
QMAKE_CC = $${CROSS_COMPILE}gcc
QMAKE_CXX = $${CROSS_COMPILE}g++
QMAKE_LINK = $${QMAKE_CXX}
QMAKE_LINK_SHLIB = $${QMAKE_CXX}
# modifications to linux.conf
QMAKE_AR = $${CROSS_COMPILE}ar cqs
QMAKE_OBJCOPY = $${CROSS_COMPILE}objcopy
QMAKE_NM = $${CROSS_COMPILE}nm -P
QMAKE_STRIP = $${CROSS_COMPILE}strip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131129/258754f8/attachment.html>
next prev parent reply other threads:[~2013-11-29 7:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 13:40 [Buildroot] [PATCH 1/2] qt5base: use -device-option to set mkspec variables Fatih Aşıcı
2013-11-14 13:40 ` [Buildroot] [PATCH 2/2] qt5base: use ccache if enabled Fatih Aşıcı
2013-11-28 22:11 ` Peter Korsgaard
2013-11-29 7:10 ` Fatih Aşıcı [this message]
2013-11-29 8:14 ` Peter Korsgaard
2013-11-29 8:26 ` Fatih Aşıcı
2013-11-18 22:41 ` [Buildroot] [PATCH 1/2] qt5base: use -device-option to set mkspec variables Arnout Vandecappelle
2013-11-20 12:22 ` Fatih Aşıcı
2013-11-20 12:17 ` [Buildroot] [PATCH v2] " Fatih Aşıcı
2013-11-20 22:18 ` Arnout Vandecappelle
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=201311290910.54807.fatih.asici@gmail.com \
--to=fatih.asici@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox