boostorg / boostorg/build

More flexible toolset matching in conditional requirements?

Ouverte
#286 5 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
transition
Langage dominant
C++
Étoiles
251
Forks
63
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

Conditional toolset requirements require an exact match, f.ex. `gcc-4.4.7:no`, but this is quite inconvenient as the full names are often illogical (the autodetected ones on Travis are `gcc-4.4.7`, `gcc-4.6`, `gcc-4.7`, `gcc-4.8` and then `gcc-4.9.4` again for some reason) and subject to constant change after minor upgrades. And the names on the test matrix are really creative.

Would it be possible to have a way to match against f.ex. `gcc` version 4.anything, or 4.4.anything? Even a simple prefix match (`gcc-4.4*`, `gcc-5*`) would work well in practice. (In principle `name-1*` would match both version 1 and version 14, but we don't have any such.)

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.