diff options
author | Samuel Martin <s.martin49@gmail.com> | 2014-08-21 22:45:20 +0200 |
---|---|---|
committer | Peter Korsgaard <peter@korsgaard.com> | 2014-09-28 20:57:26 +0200 |
commit | 47544e43a5e36f6c4ee1acb06315ab974cde78b4 (patch) | |
tree | 7e09f8b85a55523b3b9d4f70e35d9b34cd046481 /package/bash/bash-001-patchlevel27.patch | |
parent | 72d453cbfcbabcc1170713c5248d91aea4110925 (diff) | |
download | buildroot-47544e43a5e36f6c4ee1acb06315ab974cde78b4.tar.gz buildroot-47544e43a5e36f6c4ee1acb06315ab974cde78b4.zip |
toolchainfile.cmake.in: do not force the CMAKE_{C, CXX}_FLAGS to the cache
Fix #7280 [1]
When the FORCE option is passed to the set command, the variable is
added/updated in the CMake cache every single time CMake processes this
command.
Because the toolchainfile.cmake prepends architecture/toolchain flags
to the CMAKE_{C,CXX}_FLAGS, this makes the CFLAGS being updated in the
generated Makefiles each time one reconfigures its project. So it
forces the compilation of everything, even when nothing has changed.
[1] https://bugs.busybox.net/show_bug.cgi?id=7280
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Tested-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
(tested the SimpleApp reproduction scenario described in the bug report)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'package/bash/bash-001-patchlevel27.patch')
0 files changed, 0 insertions, 0 deletions