Update strong_type, v10 #15447
Update strong_type, v10 #15447
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
| @@ -23,6 +25,8 @@ def package_id(self): | |||
| def validate(self): | |||
| if self.settings.compiler.get_safe("cppstd"): | |||
| check_min_cppstd(self, 14) | |||
| if self.settings.compiler == "gcc" and Version(self.settings.compiler.version) < "7": | |||
There was a problem hiding this comment.
Is this only limited to the the newer version? the old one passed in previous PRs ?
There was a problem hiding this comment.
Yes. Previous versions did not trigger that gcc bug.
But it's not worth keeping that combination alive for old compilers and adding branches in that recipe.
Nobody using that lib is tied to such old compilers. That's a different scene, so a simpler recipe wins. (IMHO)
a4z
requested review from
uilianries and
prince-chrismc
and removed request for
prince-chrismc and
uilianries
Conan v1 pipeline ✔️All green in build 4 (
Conan v2 pipeline (informative, not required for merge) ❌
The v2 pipeline failed. Please, review the errors and note this will be required for pull requests to be merged in the near future. See details:Failure in build 4 ( An unexpected error happened and has been reported. Help is on its way! 🏇 |
* Update strong_type, v9 * Set minimum GCC to 7 * Add version v10
Specify library name and version: strong_type/v9