uci/CMakeLists.txt, branch master

CMakeLists: fix CMake warning for INCLUDE macro

2025-10-05T12:33:55Z

Fix CMake warning for INCLUDE macro by moving the INCLUDE after the PROJECT declaration. CMake Warning (dev) at /usr/share/cmake-3.31/Modules/GNUInstallDirs.cmake:253 (message): Unable to determine default CMAKE_INSTALL_LIBDIR directory because no target architecture is known. Please enable at least one language before including GNUInstallDirs. Signed-off-by: David Härdeman [ improve commit description ] Link: https://github.com/openwrt/uci/pull/7 Signed-off-by: Christian Marangi

CMakeLists: add support for including ABIVERSION in the library version number

2025-01-20T21:05:19Z

Signed-off-by: Felix Fietkau

CMakeLists.txt: bump minimum cmake version

2025-01-17T12:09:50Z

Signed-off-by: Felix Fietkau

cmake: Allow override of install directories

2021-10-22T20:58:18Z

Use the GNUInstallDirs include to allow callers to override the install directories. This is helpful when building uci in build systems like Yocto which prefer to use /usr/lib64 for the 64 bit libraries. Signed-off-by: Hauke Mehrtens

cmake: add uci-san cli built with clang sanitizers

2020-10-03T07:20:48Z

Will be used for testing. Signed-off-by: Petr Štetiar

cmake: add more hardening compiler flags

2019-12-07T22:40:02Z

In order to spot possible issues with direct impact on security during QA on CI (GCC version 6 and higher). Ref: https://developers.redhat.com/blog/2018/03/21/compiler-and-linker-flags-gcc/ Signed-off-by: Petr Štetiar

cmake: enable extra compiler checks

2019-11-14T16:11:34Z

Let's enforce additional automatic checks enforced by the compiler in order to catch possible errors during compilation. Signed-off-by: Petr Štetiar

cmake: build Lua module only if enabled

2019-11-14T16:11:08Z

Makes the resulting lua/CMakeLists.txt file simpler. Signed-off-by: Petr Štetiar

cmake: add unit testing option and shunit2 tests

2019-11-14T16:11:08Z

For convenient tests invocation. Signed-off-by: Petr Štetiar

build: Add -Wclobbered to detect problems with longjmp

2019-11-08T22:51:41Z

When we jump back to a save point in UCI_THROW() with longjmp all the registers will be reset to the old values when we called UCI_TRAP_SAVE() last time, but the memory is not restored. This will revert all the variables which are stored in registers, but not the variables stored on the stack. Mark all the variables which the compiler could put into a register as volatile to store them safely on the stack and make sure they have the defined current values also after longjmp was called. The setjmp() manage says the following: ---------------------------------------------------------------------- The compiler may optimize variables into registers, and longjmp() may restore the values of other registers in addition to the stack pointer and program counter. Consequently, the values of automatic variables are unspecified after a call to longjmp() if they meet all the following criteria: * they are local to the function that made the corresponding setjmp() call; * their values are changed between the calls to setjmp() and longjmp(); and * they are not declared as volatile. --------------------------------------------------------------------- The -Wclobbered compiler option warns about all variables which are written after setjmp() was called, not all of them could cause problems, but to make sure to catch all real problems add this warning and fix all occurrences of this warning. This also activates a compiler warning which should warn us in such cases. This could fix some potential problems in error paths like the one reported in CVE-2019-15513. Signed-off-by: Hauke Mehrtens