boostorg / boostorg/build

More flexible toolset matching in conditional requirements?

Abierto
#286 5 comentarios 0 reacciones 0 asignados Ver en GitHub
transition
Lenguaje dominante
C++
Estrellas
251
Forks
63
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.