simon-git: puzzles (main): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  7ad37c6 Fix build under cmake -G 'Ninja Multi-Config'.

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:           2026-05-22 16:19:30

commit 7ad37c64af3bc891372ec16db1531cee599b6e3a
web diff https://git.tartarus.org/?p=simon/puzzles.git;a=commitdiff;h=7ad37c64af3bc891372ec16db1531cee599b6e3a;hp=06e37f1e334d85c7c779f79ef9e484ff2f708269
Author: Simon Tatham <anakin at pobox.com>
Date:   Fri May 22 16:11:05 2026 +0100

    Fix build under cmake -G 'Ninja Multi-Config'.
    
    This cmake generator has the unusual property that it writes out
    multiple build scripts (e.g. build-Debug.ninja and
    build-Release.ninja) which can be run within the same build directory
    without colliding with each other's build products, by putting debug
    and release binaries in subdirectories of CMAKE_BINARY_DIR, e.g.
    Debug/foo and Release/foo.
    
    The build step that runs each puzzle's "icon-maker" variant to make a
    screenshot for the puzzle's icon was referring to those icon-maker
    binaries as ${icon_bindir}/${name}-icon-maker, on the assumption that
    all cmake generators would drop the binary in the obvious build
    directory. In this case, it doesn't. We can find the file no matter
    where it ends up using cmake's $<TARGET_FILE:...> syntax.
    
    Thanks to Josh Lee for the report and the one-line fix.

 icons/icons.cmake | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)