cmake presets are not usable (at leased on OSX)

[ClausKlein]

bash-3.2$ cmake --preset=unixlike-gcc-release
Preset CMake variables:

  CMAKE_BUILD_TYPE="RelWithDebInfo"
  CMAKE_CXX_COMPILER="g++"
  CMAKE_C_COMPILER="gcc"
  CMAKE_INSTALL_PREFIX:PATH="/Users/clausklein/Workspace/cpp/cpp_boilerplate_project/out/install/unixlike-gcc-release"

-- The CXX compiler identification is AppleClang 13.1.6.13160021
-- The C compiler identification is AppleClang 13.1.6.13160021
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Developer mode is ON. For production, use `-DENABLE_DEVELOPER_MODE:BOOL=OFF`. Building the project for the developer...
-- The default CMAKE_C_STANDARD used by external targets and tools is not set yet. Using the latest supported C standard that is 17
-- /usr/local/bin/ccache found and enabled
-- Downloading conan.cmake from https://github.com/conan-io/cmake-conan
-- Conan: Adding cci remote repository (https://center.conan.io) verify ssl (True)
-- Conan: Adding bincrafters remote repository (https://bincrafters.jfrog.io/artifactory/api/conan/public-conan) verify ssl (True)
-- Single configuration build!
-- Running Conan for build type 'RelWithDebInfo'
-- Conan: checking conan executable
-- Conan: Found program /usr/local/bin/conan
-- Conan: Version found Conan version 1.47.0
-- Conan executing: /usr/local/bin/conan install /Users/clausklein/Workspace/cpp/cpp_boilerplate_project --build missing --env CC=/usr/bin/gcc --env CXX=/usr/bin/g++ --settings build_type=RelWithDebInfo --settings compiler=apple-clang --settings compiler.version=13.1 --settings compiler.libcxx=libc++ --settings compiler.cppstd=20
-- Dependency fmt already found
-- Library docopt found /Users/clausklein/.conan/data/docopt.cpp/0.6.3/_/_/package/5daf637a62aba772e1702099bde4503471cf3546/lib/libdocopt.dylib
-- Found: /Users/clausklein/.conan/data/docopt.cpp/0.6.3/_/_/package/5daf637a62aba772e1702099bde4503471cf3546/lib/libdocopt.dylib
-- Library docopt found /Users/clausklein/.conan/data/docopt.cpp/0.6.3/_/_/package/5daf637a62aba772e1702099bde4503471cf3546/lib/libdocopt.dylib
-- Found: /Users/clausklein/.conan/data/docopt.cpp/0.6.3/_/_/package/5daf637a62aba772e1702099bde4503471cf3546/lib/libdocopt.dylib
CMake Warning (dev) at CMakeLists.txt:129 (message):
  Building Tests.  Be sure to check out test/constexpr_tests.cpp for
  constexpr testing
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done
-- Generating done
-- Build files have been written to: /Users/clausklein/Workspace/cpp/cpp_boilerplate_project/out/build/unixlike-gcc-release
bash-3.2$ cmake --build --preset=unixlike-gcc-release
CMake Error: No such build preset in /Users/clausklein/Workspace/cpp/cpp_boilerplate_project: "unixlike-gcc-release"
########################################################################################

bash-3.2$ ctest --build --preset=unixlike-gcc-release
CMake Error: No such test preset in /Users/clausklein/Workspace/cpp/cpp_boilerplate_project: "unixlike-gcc-release"
Available test presets:

  "test-windows-msvc-debug-developer-mode"   - Strict
  "test-windows-msvc-release-developer-mode" - Strict
  "test-windows-clang-debug"                 - Strict
  "test-windows-clang-release"               - Strict
  "test-unixlike-gcc-debug"                  - Strict
  "test-unixlike-gcc-release"                - Strict
  "test-unixlike-clang-debug"                - Strict
  "test-unixlike-clang-release"              - Strict
bash-3.2$ 

[lefticus]

Re: @Jason5480

[ClausKlein]

something like this is missing:

  "buildPresets": [
    {
      "name": "test",
      "configurePreset": "test"
    },
    {
      "name": "ninja-multi",
      "configurePreset": "ninja-multi"
    }
  ],
  "testPresets": [
    {
      "name": "test",
      "configurePreset": "test",
      "output": {"outputOnFailure": true},
      "execution": {"noTestsAction": "error", "stopOnFailure": true}
    },
    {
      "name": "ninja-multi",
      "configurePreset": "ninja-multi",
      "inherits": "test"
    }
  ]

[Jason5480]

@ClausKlein the testPreset corresponding to the 'unixlike-gcc-release' configurePreset is the 'test-unixlike-gcc-release' so this is the name that should be passed to the ctest command.

[Jason5480]

something like this is missing:

If you use a multi config generator, then buildPresets are needed. But with a simple Ninja generator you do not have to pass a preset to the build stage. I have a PR that does that for "Ninja Multi-Config" generator but is still pending #19. @ClausKlein please if you have some time check if this work on OSX since I cannot check that.

[ClausKlein]

@Jason5480 I can't use it to configure the build!

bash-3.2$ git status
On branch feature/ninja-multi-presets-support
Your branch is up to date with 'Nikolas/feature/ninja-multi-presets-support'.

nothing to commit, working tree clean
bash-3.2$ cmake -S . --list-presets=all

Available build presets:

  "build-windows-msvc-debug"   - Debug
  "build-windows-msvc-release" - Release
  "build-linux-gcc-debug"      - Debug
  "build-linux-gcc-release"    - Release
  "build-linux-clang-debug"    - Debug
  "build-linux-clang-release"  - Release

Available test presets:

  "test-windows-msvc-debug"   - Debug
  "test-windows-msvc-release" - Release
  "test-linux-gcc-debug"      - Debug
  "test-linux-gcc-release"    - Release
  "test-linux-clang-debug"    - Debug
  "test-linux-clang-release"  - Release
bash-3.2$ 

[ClausKlein]

with a little love, is seems better:

bash-3.2$ cmake -S . --list-presets=all
Available configure presets:

  "linux-gcc"   - gcc
  "linux-clang" - clang

Available build presets:

  "build-windows-msvc-debug"   - Debug
  "build-windows-msvc-release" - Release
  "build-linux-gcc-debug"      - Debug
  "build-linux-gcc-release"    - Release
  "build-linux-clang-debug"    - Debug
  "build-linux-clang-release"  - Release

Available test presets:

  "test-windows-msvc-debug"   - Debug
  "test-windows-msvc-release" - Release
  "test-linux-gcc-debug"      - Debug
  "test-linux-gcc-release"    - Release
  "test-linux-clang-debug"    - Debug
  "test-linux-clang-release"  - Release
bash-3.2$ git diff

diff --git a/CMakePresets.json b/CMakePresets.json
index a33a880..9d237b3 100644
--- a/CMakePresets.json
+++ b/CMakePresets.json
@@ -35,17 +35,7 @@
             "name": "config-linux-common",
             "description": "Linux settings for gcc and clang toolchains",
             "hidden": true,
-            "inherits": "config-common",
-            "condition": {
-                "type": "equals",
-                "lhs": "${hostSystemName}",
-                "rhs": "Linux"
-            },
-            "vendor": {
-                "microsoft.com/VisualStudioRemoteSettings/CMake/1.0": {
-                    "sourceDir": "$env{HOME}/.vs/$ms{projectDirName}"
-                }
-            }
+            "inherits": "config-common"
         },
         {
             "name": "windows-msvc",
@@ -231,4 +221,4 @@
             "configurePreset": "linux-clang"
         }
     ]
-}
\ No newline at end of file
+}
bash-3.2$ 

[ClausKlein]

What is the concept behind your presets?
Missing buildDir but a sourceDir configured?
Long and different presetNames?
I would expect the same name for the same preset in config, build, and test part.

bash-3.2$ cmake -S . --preset=linux-common
CMake Error: No such preset in /Users/clausklein/Workspace/cpp/cpp_boilerplate_project: "linux-common"
Available configure presets:

  "linux-gcc"   - gcc
  "linux-clang" - clang
bash-3.2$ cmake -S . --preset=linux-gcc   
Preset CMake variables:

  CMAKE_BUILD_TYPE="Debug"
  CMAKE_CXX_COMPILER="g++"
  CMAKE_C_COMPILER="gcc"

######################################################
Warning: in-source builds are disabled
Please create a separate build directory and run cmake from there
######################################################
CMake Error at _deps/_project_options-src/src/PreventInSourceBuilds.cmake:15 (message):
  Quitting configuration
Call Stack (most recent call first):
  _deps/_project_options-src/src/PreventInSourceBuilds.cmake:19 (assure_out_of_source_builds)
  _deps/_project_options-src/src/Index.cmake:7 (include)
  _deps/_project_options-src/Index.cmake:1 (include)
  CMakeLists.txt:29 (include)


-- Configuring incomplete, errors occurred!
bash-3.2$ pwd
/Users/clausklein/Workspace/cpp/cpp_boilerplate_project
bash-3.2$ 

[ClausKlein]

I have this on my ModernCmakeStarter:

bash-3.2$ cmake -S . --list-presets=all
Available configure presets:

  "test"        - Test Config
  "ninja-multi" - Ninja Multi-Config

Available build presets:

  "test"
  "ninja-multi"

Available test presets:

  "test"
  "ninja-multi"
bash-3.2$ 

[ClausKlein]

If I add this line: "binaryDir": "${sourceDir}/build", I can configure, but not build!

[ClausKlein]

@Jason5480 Only if have the same names for associated presets, it works:

bash-3.2$ cmake -S . --list-presets=all
Available configure presets:

  "linux-gcc"   - gcc
  "linux-clang" - clang

Available build presets:

  "build-windows-msvc-debug"   - Debug
  "build-windows-msvc-release" - Release
  "linux-gcc"                  - Debug
  "linux-clang"                - Debug

Available test presets:

  "test-windows-msvc-debug"   - Debug
  "test-windows-msvc-release" - Release
  "linux-gcc"                 - Debug
  "linux-clang"               - Debug
bash-3.2$ 

[Jason5480]

@Jason5480 I can't use it to configure the build!

bash-3.2$ git status
On branch feature/ninja-multi-presets-support
Your branch is up to date with 'Nikolas/feature/ninja-multi-presets-support'.

nothing to commit, working tree clean
bash-3.2$ cmake -S . --list-presets=all

Available build presets:

  "build-windows-msvc-debug"   - Debug
  "build-windows-msvc-release" - Release
  "build-linux-gcc-debug"      - Debug
  "build-linux-gcc-release"    - Release
  "build-linux-clang-debug"    - Debug
  "build-linux-clang-release"  - Release

Available test presets:

  "test-windows-msvc-debug"   - Debug
  "test-windows-msvc-release" - Release
  "test-linux-gcc-debug"      - Debug
  "test-linux-gcc-release"    - Release
  "test-linux-clang-debug"    - Debug
  "test-linux-clang-release"  - Release
bash-3.2$ 

I was talking about the Jason5480:feature/presets-enchancements branch.

[Jason5480]

@Jason5480 Only if have the same names for associated presets, it works:

That is strange... your IDE should let you choose between different configure, build and test Presets. At least this is what VSCode and Visual Studio do. What IDE do you use? or you run cmake commands directly?

[ClausKlein]

@Jason5480 OK, tomorrow I will hav a look

P.S. I working on console and with gvim, or Xcode

[Jason5480]

What is the concept behind your presets?
...
CMake presets are just a bundle of configuration/flags that can be passed in CMake during the configuration, build and test phases accordingly and also can be shared with the team. The changes I propose here Jason5480:feature/presets-enchancements just change the generator from "Ninja" to "Ninja Multi-Config". The diference with the multi-config generators is that you define the Debug/Release during the build stage and not during the configuration as you do with regular generators but this should not affect your use case.

Missing buildDir but a sourceDir configured?
...
Usually, each IDE passes its own default dirs. If you run from the cli you can pass the -B -S.

Long and different presetNames? I would expect the same name for the same preset in config, build, and test part.
...
For the multi-config generator case this cannot be done because for each configuration preset you have at least two build presets, one for the Release and one for the Debug build. The names of those build Presets should be different.

[Jason5480]

@Jason5480 OK, tomorrow I will hav a look

P.S. I working on console and with gvim, or Xcode

I tried those commands in Jason5480:feature/presets-enchancements and worked as expected in a Linux docker image (provided in the .devcontainer folder)

`cmake --preset=unixlike-gcc-release

cmake --build --preset=build-unixlike-gcc-release

ctest --build --preset=test-unixlike-gcc-release`

The equivalent for this repository should be
`cmake --preset=unixlike-gcc-release

cmake --build

ctest --build --preset=test-unixlike-gcc-release`

However, I did not test the later case.