simon-git: puzzles (main): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  c0c64dc Advertise user-configurable cmake-time config options.

Repository:     https://git.tartarus.org/simon/puzzles.git
On the web:     https://git.tartarus.org/?p=simon/puzzles.git
Branch updated: main
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2021-04-04 15:08:15

commit c0c64dc1051bcbdd3ffe839f63d6c609ea5954e6
web diff https://git.tartarus.org/?p=simon/puzzles.git;a=commitdiff;h=c0c64dc1051bcbdd3ffe839f63d6c609ea5954e6;hp=c212b4eda364ba17f2ff34f4958bfb49d0de258c
Author: Simon Tatham <anakin at pobox.com>
Date:   Sun Apr 4 14:58:39 2021 +0100

    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.

 cmake/platforms/unix.cmake | 20 ++++++++++++++++----
 cmake/setup.cmake          |  4 ++++
 2 files changed, 20 insertions(+), 4 deletions(-)