aboutsummaryrefslogtreecommitdiff
path: root/cmake/setup.cmake
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2021-04-04 14:58:39 +0100
committerSimon Tatham <anakin@pobox.com>2021-04-04 14:58:39 +0100
commitc0c64dc1051bcbdd3ffe839f63d6c609ea5954e6 (patch)
treec50ae63b962c511ec7b6b380f978d0109afb5f49 /cmake/setup.cmake
parentc212b4eda364ba17f2ff34f4958bfb49d0de258c (diff)
downloadpuzzles-c0c64dc1051bcbdd3ffe839f63d6c609ea5954e6.zip
puzzles-c0c64dc1051bcbdd3ffe839f63d6c609ea5954e6.tar.gz
puzzles-c0c64dc1051bcbdd3ffe839f63d6c609ea5954e6.tar.bz2
puzzles-c0c64dc1051bcbdd3ffe839f63d6c609ea5954e6.tar.xz
Advertise user-configurable cmake-time config options.
Various cmake variables that I was informally expecting users to set on the cmake command line (e.g. cmake -DSTRICT=ON, or cmake -DPUZZLES_GTK_VERSION=2) are now labelled explicitly with the CACHE tag, and provided with a documentation string indicating what they're for. One effect of this is that GUI-like interfaces to your cmake build directory, such as ccmake or cmake-gui, will show those variables explicitly to give you a hint that you might want to change them. Another is that when you do change them, cmake will recognise that it needs to redo the rest of its configuration. Previously, if you sat in an existing cmake build directory and did 'cmake -DSTRICT=ON .' followed by 'cmake -DSTRICT=OFF .', nothing would happen, even though you obviously meant it to.
Diffstat (limited to 'cmake/setup.cmake')
-rw-r--r--cmake/setup.cmake4
1 files changed, 4 insertions, 0 deletions
diff --git a/cmake/setup.cmake b/cmake/setup.cmake
index d9c7663..0ccf345 100644
--- a/cmake/setup.cmake
+++ b/cmake/setup.cmake
@@ -1,3 +1,7 @@
+set(PUZZLES_ENABLE_UNFINISHED ""
+ CACHE STRING "List of puzzles in the 'unfinished' subdirectory \
+to build as if official (separated by ';')")
+
set(build_individual_puzzles TRUE)
set(build_cli_programs TRUE)
set(build_icons FALSE)