From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7280] New: CMake toolchain file uses the FORCE attribute on CMAKE_CXX_FLAGS
Date: Thu, 24 Jul 2014 10:12:18 +0000 (UTC) [thread overview]
Message-ID: <bug-7280-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7280
Summary: CMake toolchain file uses the FORCE attribute on
CMAKE_CXX_FLAGS
Product: buildroot
Version: 2014.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: deblauwetom+buildroot at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
It seems the cmake toolchain file generated by buildroot uses "FORCE" to set
the CXX and C flags. However, this can be a problem. The toolchain file is read
every run of cmake, so the CXX flags keep growing. This results in a complete
rebuild everytime something changes in a CMakeLists.txt. CMake correctly thinks
that it must rebuild everything because the CMAKE_CXX_FLAGS must be applied to
all which you are compiling. It can be solved by removing the FORCE attribute
of the set() command. The same goes for the CMAKE_C_FLAGS.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-07-24 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 10:12 bugzilla at busybox.net [this message]
2014-07-24 12:43 ` [Buildroot] [Bug 7280] CMake toolchain file uses the FORCE attribute on CMAKE_CXX_FLAGS bugzilla at busybox.net
2014-07-24 12:57 ` bugzilla at busybox.net
2014-08-09 11:30 ` bugzilla at busybox.net
2014-08-09 11:52 ` bugzilla at busybox.net
2014-08-16 13:43 ` bugzilla at busybox.net
2014-09-02 8:40 ` bugzilla at busybox.net
2014-10-20 19:13 ` bugzilla at busybox.net
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=bug-7280-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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