summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHauke Mehrtens2026-02-15 23:49:15 +0000
committerHauke Mehrtens2026-02-17 00:29:57 +0000
commit7bf8d568f6c83411041e504e0ca231d4081c2534 (patch)
treeb0798f6e10a753541c28bc9004e64bfc7175d3ef
parentb23726664090098acb9318caf41f7d6961cd1074 (diff)
downloadopenwrt-7bf8d568f6c83411041e504e0ca231d4081c2534.tar.gz
build: pass CPPFLAGS to cmake build
The TARGET_CPPFLAGS contain the include paths used by OpenWrt. This also contains the including of the fortify sources headers. If they are not provided, the applications will not use fortify sources headers when compiled against musl. Add them to cmake builds too. cmake does not support a special CPPFLGS option [0], just add them to CFLAGS and CXXFLAGS like we also do it for meson and normal make. This should fix fortify sources support for cmake builds. I found this explanation for the flags: * CFLAGS: C flags, passed during compile AND link * CXXFLAGS: C++ flags, passed during compile AND link * CPPFLAGS: pre-processor flags, passed ONLY during compile * LDFLAGS: linker flags, passed ONLY during link [0]: https://gitlab.kitware.com/cmake/cmake/-/issues/12928 Link: https://github.com/openwrt/openwrt/pull/22042 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
-rw-r--r--include/cmake.mk4
1 files changed, 2 insertions, 2 deletions
diff --git a/include/cmake.mk b/include/cmake.mk
index b6e485eb4f..29c5aacb83 100644
--- a/include/cmake.mk
+++ b/include/cmake.mk
@@ -89,8 +89,8 @@ endif
define Build/Configure/Default
mkdir -p $(CMAKE_BINARY_DIR)
(cd $(CMAKE_BINARY_DIR); \
- CFLAGS="$(TARGET_CFLAGS) $(EXTRA_CFLAGS)" \
- CXXFLAGS="$(TARGET_CXXFLAGS) $(EXTRA_CXXFLAGS)" \
+ CFLAGS="$(TARGET_CFLAGS) $(EXTRA_CFLAGS) $(TARGET_CPPFLAGS) $(EXTRA_CPPFLAGS)" \
+ CXXFLAGS="$(TARGET_CXXFLAGS) $(EXTRA_CXXFLAGS) $(TARGET_CPPFLAGS) $(EXTRA_CPPFLAGS)" \
LDFLAGS="$(TARGET_LDFLAGS) $(EXTRA_LDFLAGS)" \
cmake \
--no-warn-unused-cli \