Details
-
Suggestion
-
Resolution: Fixed
-
Not Evaluated
-
None
-
2.2.2
-
None
-
-
176c4e123 (2.3)
Description
I have the following build tools on my machine:
- MSVS 2017 (i need to built smth for Win XP :/);
- MSVS 2019 with clang-cl and MSVC (msvc is my default toolchain for building);
- MSVS 2022 with clang-cl and MSVC (i want to move to clang-cl from MSVS 2022);
- Standalone LLVM 13 in PATH (fixed version for clang-format, clang-tidy and clangd).
qbs setup-toolchains --detect creates profiles for MSVC 2017, MSVC 2019, MSVC2022 and standalone LLVM. If I remove standalone LLVM installation, cland-cl profile will be created for MSVS 2019 or MSVS 2022 clang-cl installation.
All MSVC profiles can be created in range-based for after probing (even if I'll install several MSVS 2022). Clang-cl profile will be created for the first clang-cl in PATH. Can this behavior be changed? It will be awesome if autogenerated profiles would contain MSVS binding in their name (if any) but simply clang-cl-[123]-x86 would be ok.