Inspecting cmake presets options not available in cmake 4.x

[OmBiradar]

I was trying to build arrow C++, here in the docs, the command cmake --preset -N ninja-debug-minimal outputs nothing,,,

System:
Arch linux x86
cmake version 4.2.3

Component(s)

C++ | Docs

[raulcd]

What does it mean, outputs nothing? If I use a random cmake command with a non-existent preset I get an error:

$ cmake --preset -N random
CMake Error: Could not read presets from /home/user/tmp:
File not found: /home/user/tmp/CMakePresets.json

Can you share your command and the output?

[OmBiradar]

$ cmake -N --preset ninja-debug-minimal

This is run in the directory arrow/cpp

it doesn't return any response while the docs specify that it should list the configuration of the preset "ninja-debug-minimal"

while

$ cmake --preset -N random
CMake Error: No such preset in /home/ink/DEV/arrow/cpp: "random"                            Available configure presets:

  "ninja-debug-minimal"           - Debug build without anything enabled                      "ninja-debug-basic"             - Debug build with tests and reduced dependencies
  "ninja-debug"                   - Debug build with tests and more optional components
  "ninja-debug-cuda"              - Debug build with tests and CUDA integration               "ninja-debug-filesystems"       - Debug build with tests and filesystems
  "ninja-debug-flight"            - Debug build with tests and Flight
  "ninja-debug-flight-sql"        - Debug build with tests and Flight SQL                     "ninja-debug-flight-sql-odbc"   - Debug build with tests and Flight SQL ODBC
  "ninja-debug-gandiva"           - Debug build with tests and Gandiva
  "ninja-debug-python-minimal"    - Debug build for PyArrow with minimal features
  "ninja-debug-python"            - Debug build for PyArrow with common features (for backward compatibility)
  "ninja-debug-python-maximal"    - Debug build for PyArrow with everything enabled
  "ninja-debug-maximal"           - Debug build with everything enabled (except benchmarks)
  "ninja-debug-emscripten"        - Debug build which builds an Emscripten library
  "ninja-debug-valgrind-minimal"  - Debug build for Valgrind without anything enabled
  "ninja-debug-valgrind-basic"    - Debug build for Valgrind with tests and reduced dependencies
  "ninja-debug-valgrind"          - Debug build for Valgrind with tests and more optional components
  "ninja-debug-valgrind-maximal"  - Debug build for Valgrind with tests and everything enabled
  "ninja-debug-asan"              - Debug build for ASAN with tests and more optional components
  "ninja-debug-tsan"              - Debug build for TSAN with tests and more optional components
  "ninja-debug-ubsan"             - Debug build for UBSAN with tests and more optional components
  "fuzzing"                       - Debug build with IPC and Parquet fuzzing targets
  "ninja-release-minimal"         - Release build without anything enabled
  "ninja-release-basic"           - Release build with reduced dependencies
  "ninja-release"                 - Release build with more optional components
  "ninja-release-cuda"            - Release build with CUDA integration
  "ninja-release-flight"          - Release build with Flight
  "ninja-release-flight-sql"      - Release build with Flight SQL
  "ninja-release-flight-sql-odbc" - Release build with Flight SQL ODBC
  "ninja-release-gandiva"         - Release build with Gandiva
  "ninja-release-python-minimal"  - Release build for PyArrow with minimal features
  "ninja-release-python"          - Release build for PyArrow with common features (for backward compatibility)
  "ninja-release-python-maximal"  - Release build for PyArrow with everything enabled
  "ninja-release-maximal"         - Release build with everything enabled (except benchmarks)
  "ninja-release-emscripten"      - Release build which builds an Emscripten library
  "ninja-benchmarks-basic"        - Benchmarking build with reduced dependencies
  "ninja-benchmarks"              - Benchmarking build with more optional components
  "ninja-benchmarks-maximal"      - Benchmarking build with everything enabled
  "ninja-release-jni-linux"       - Build for JNI on Linux
  "ninja-release-jni-macos"       - Build for JNI on macOS

[raulcd]

ok! I understand now, thanks for raising! yes, there seems to be something wrong with the view-only (-N) mode where the CMake variables are not shown anymore:

$ cmake --preset ninja-debug -N
$

[OmBiradar]

this might be helpful, tho I don't know what to infer from this. I use cmake but I am not very familiar with how it "exactly" works internally

https://cmake.org/cmake/help/latest/manual/cmake.1.html#:~:text=%2DN,and%20generate%20steps.