boostorg / boostorg/build

More flexible toolset matching in conditional requirements?

Offen
#286 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
transition
Vorherrschende Sprache
C++
Sterne
251
Forks
63
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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.)

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.