Currently, cargo-wdk exposes CLI options to configure the build, e.g. --target-architecture, --target-platform, --stampinf-args. There is no way, other than the full cargo wdk build invocation, to specify/record how a particular driver must be built.
For e.g. if a driver is built with
cargo wdk build --target-platform desktop --sample --inf2cat-args '/os:10_x64'
Developers and CI must know and use exact command. Further, the passthrough flags take raw quoted strings which could lead to long command lines. With workspaces, mixed workspaces (driver + non-driver) the problem becomes larger.
In order to cater to these issues, cargo-wdk can support a way to configure the build and packaging options through a file, so that plain cargo wdk build produces a correct package.
Currently,
cargo-wdkexposes CLI options to configure the build, e.g.--target-architecture,--target-platform,--stampinf-args. There is no way, other than the fullcargo wdk buildinvocation, to specify/record how a particular driver must be built.For e.g. if a driver is built with
Developers and CI must know and use exact command. Further, the passthrough flags take raw quoted strings which could lead to long command lines. With workspaces, mixed workspaces (driver + non-driver) the problem becomes larger.
In order to cater to these issues,
cargo-wdkcan support a way to configure the build and packaging options through a file, so that plaincargo wdk buildproduces a correct package.