-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[package] <fmt>/<8.1.1>: Invalid setting 'baremetal' is not a valid 'settings.os' value. #9058
Comments
Same thing happening for fmt/8.0.1 Package and Environment Details (include every applicable attribute)
Conan profile
|
Your This issue is similar to #8550 /cc @memsharded @lasote, because it refers to how conan handles missing os or compiler identifier in settings.yml |
I don't think that's it. I've cleaned entire local Conan cache just in case and the issue is still happening. But I'll check it out once more tomorrow. |
At least it's in the release note of conan 1.43.0: https://github.com/conan-io/conan/releases/tag/1.43.0 |
I had the similar issue and the solution that worked for me was: |
@JorgenPo Thanks, I confirm that updating |
Package and Environment Details (include every applicable attribute)
Conan profile (output of
conan profile show default
orconan profile show <profile>
if custom profile is in use)Steps to reproduce (Include if Applicable)
Try to install fmt/8.1.1
Fmt can't be installed for me anymore. It seems this recipe is incorrect to the current Conan version
https://conan.io/center/fmt?tab=recipe
Conan raises the following error:
ERROR: fmt/8.1.1: Error in config_options() method, line 52
elif self.settings.os == "baremetal":
ConanException: Invalid setting 'baremetal' is not a valid 'settings.os' value.
Possible values are ['AIX', 'Android', 'Arduino', 'Emscripten', 'FreeBSD', 'Linux', 'Macos', 'Neutrino', 'SunOS', 'Windows', 'WindowsCE', 'WindowsStore', 'iOS', 'tvOS', 'watchOS']
Read "http://docs.conan.io/en/latest/faq/troubleshooting.html#error-invalid-setting"
The text was updated successfully, but these errors were encountered: