You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing CI scripts it is useful to be able to specify some compiler flags in a matrix variable.
If for a given row in the matrix, there are no flags to set this becomes a problem because currently cxxflags=
is an invalid command line component for b2.
A workaround is to include the cxxflags in the matrix variable, i.e.
Note for future reference: This would likely be implemented in the property argument parsing code. It would need to translate feature-name= to either: ignoring the argument for optional features as the value is empty, or allowing an empty value for free features instead an error. Doing the second one is problematic as it would be a likely breaking change as it contrary to existing practice. Which, of note, would be the case for this request as cxxflags is a free feature.
Make sure you completed the following tasks
Environment and version details
All
Describe your use case
When writing CI scripts it is useful to be able to specify some compiler flags in a matrix variable.
If for a given row in the matrix, there are no flags to set this becomes a problem because currently
cxxflags=
is an invalid command line component for b2.
A workaround is to include the cxxflags in the matrix variable, i.e.
followed by:
But this feels suboptimal as it splits logic across the script.
Describe the solution you'd like
I would like this to work:
Which would then build
target
with no additional command line flags set. i.e. it would be identical to writing:The text was updated successfully, but these errors were encountered: