The -C,--compiler-cli <VALUE> and -L,--linker-cli <VALUE> options would pass the <VALUE> to the compiler (candle.exe) and linker (light.exe) as CLI options. There are many CLI options and flags for both the compiler and the linker. It does not make sense to re-implement every CLI option and flag into the default create subcommand. This is just a lot of redundant work, and some of it would be complicated given that the default create subcommand is a 2in1, where it calls both the compiler and linker with one command. However, there needs to be a mechanism for users for the cargo-wix subcommand to invoke some of the CLI options and flags of the compiler and linker for their specific use cases.

In other words, there are going to be some edge cases where users need some specific CLI option or flag but I do not want to have implement each of these edge cases. I think the easiest way to handle this is to provide options that "pass" options or flags onto the compiler and linker, similar to the -- positional argument for some of the Cargo subcommands that pass through arguments. While the -- would be relatively easy to implement, it would not be able to handle the 2in1 situation. How would you pass a linker option to the linker and the not the compiler with the -- argument? Thus, separate, explicit options are needed.

An example invocation:

C:\Path\to\Project> cargo wix -C "-ext UserCompilerExtension" -L "-ext UserLinkerExtension"

Both options could be used multiple times, but note the quotes since there is space in the value. This example would of course eliminate the need for #95.