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
CBI currently has very limited support for emulating the behaviors of other compilers. There are some hard-coded configurations in config.py, and users can provide unconditional definitions via the .cbi/config file.
We should provide a mechanism that allows users to define compiler behavior more precisely (e.g., by defining the behavior of specific flags). For example, a user could define that -std={something} defines a specific set of macros that are important to their application.
Request attributes
Would this be a refactor of existing code?
Does this proposal require new package dependencies?
Feature/behavior summary
CBI currently has very limited support for emulating the behaviors of other compilers. There are some hard-coded configurations in
config.py
, and users can provide unconditional definitions via the.cbi/config
file.We should provide a mechanism that allows users to define compiler behavior more precisely (e.g., by defining the behavior of specific flags). For example, a user could define that
-std={something}
defines a specific set of macros that are important to their application.Request attributes
Related issues
Solution description
Extend the
.cbi/config
schema to support the definition of additional compiler arguments.One possibility would be to draw inspiration from
argparse
, supporting syntax like:...but with a limited set of supported
destination
andaction
strings.Additional notes
No response
The text was updated successfully, but these errors were encountered: