Bug description
Whenever a multi-config generator is used (e.g. Ninja Multi-Config), running :CMakeRun will always run the binary in ./build/bin/Debug. Using :CMakeSelectBuildType doesn't change anything. Maybe :CMakeSelectRunConfig should be added?
Steps to reproduce
- Create a
CMakePresets.json file with a configurePresets entry using the Ninja Multi-Config generator
- In the
CMakePresets.json, add 2 buildPresets entries, one with "configuration": "Debug", and one with "configuration": "Release"
- Run
:CMakeGenerate
- Run
:CMakeSelectBuildPreset and select the release preset you added to your buildPresets.
- Run
:CMakeBuild
- Run
:CMakeRun, notice that the binary in ./build/bin/Debug is being ran
Expected behaviour
:CMakeRun should use the binary generated by :CMakeBuild, according to the configuration specified in the buildPresets entry.
Screenshots
N/a
Environment
- OS: Arch Linux
- Desktop environment: KDE
- Plugins commit hash: 98cdc16
Contents in the *cmake-tools* buffer
N/a
Bug description
Whenever a multi-config generator is used (e.g. Ninja Multi-Config), running
:CMakeRunwill always run the binary in./build/bin/Debug. Using:CMakeSelectBuildTypedoesn't change anything. Maybe:CMakeSelectRunConfigshould be added?Steps to reproduce
CMakePresets.jsonfile with aconfigurePresetsentry using theNinja Multi-ConfiggeneratorCMakePresets.json, add 2buildPresetsentries, one with"configuration": "Debug", and one with"configuration": "Release":CMakeGenerate:CMakeSelectBuildPresetand select the release preset you added to yourbuildPresets.:CMakeBuild:CMakeRun, notice that the binary in./build/bin/Debugis being ranExpected behaviour
:CMakeRunshould use the binary generated by:CMakeBuild, according to the configuration specified in thebuildPresetsentry.Screenshots
N/a
Environment
Contents in the *cmake-tools* buffer
N/a