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
Currently, drivers built off of windows-drivers-rs only allow conditional compilation based off of driver type (example). This can be easily expanded to other parts of the Wdk config struct via adding those fields to EXPORTED_CFG_SETTINGS.
When adding cfg's for UMDF/KMDF Version, usability in driver code can be less than ideal. For example, it is not easy to conditional compile for Minor versions less than 7. Rust's cfg system only allows for cfg being equal to a value. Instead, you would have to have multiple cfg clauses for each value that are all "or"ed together via any.
This is very painful to use. One possible solution to this could be to get wdk-build to generate some sort of cfg aliases for ranges via something like cfg_aliases.
The text was updated successfully, but these errors were encountered:
Currently, drivers built off of windows-drivers-rs only allow conditional compilation based off of driver type (example). This can be easily expanded to other parts of the
Wdk
config struct via adding those fields toEXPORTED_CFG_SETTINGS
.When adding cfg's for UMDF/KMDF Version, usability in driver code can be less than ideal. For example, it is not easy to conditional compile for Minor versions less than 7. Rust's cfg system only allows for
cfg
being equal to a value. Instead, you would have to have multiplecfg
clauses for each value that are all "or"ed together viaany
.Example:
This is very painful to use. One possible solution to this could be to get
wdk-build
to generate some sort of cfg aliases for ranges via something likecfg_aliases
.The text was updated successfully, but these errors were encountered: