-
Notifications
You must be signed in to change notification settings - Fork 990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[question] Why does CMakeToolchain's cache_variables
convert recipe options to CMake bool but variables
converts them to strings?
#14590
Comments
cache_variables
convert options to CMake bool and variables
doesn't?cache_variables
convert recipe options to CMake bool and variables
converts them to strings?
cache_variables
convert recipe options to CMake bool and variables
converts them to strings?cache_variables
convert recipe options to CMake bool but variables
converts them to strings?
@memsharded Should I generate a bug report with more info maybe? |
Hi, @tgurriet - Thanks a lot for the report. Yes, this is known. CMakeToolchain has a mechanism to convert raw options for the |
Sounds good, thanks! |
We have been checking this:
The solution to make them behave similar would be to force the I am closing this ticket as responded, but please re-open or create a new one for any further question. |
What is your question?
Hello,
While exploring the files generated by the CMakeToolchain generator, I realized that when assigning an option to
cache_variables
, it resulted in a CMakeboolean
variable in theCMakePresets.json
, wherease passing the same option tovariables
generated a CMakestring
variable in theconan_toolchain.cmake
.Is there a reason for that difference? I couldn't find anything in the doc about this.
The recipe:
The generated CMakePresets.json:
The generated conan_toolchain.cmake:
Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: