Christopher Field

@chaynabors Thank you for your interest and usage of this cargo subcommand. You are not missing anything. There is no `-p` option or support for the `cargo wix sign` sub-sub-command....

I was not aware of the msitools project. It looks interesting. It looks like the `wixl` command is a one-step compile/build command, while WiX Toolset is a two-step compile/link command....

This sounds like you are hitting #135 and ultimately related to https://github.com/rust-lang/cargo/issues/9357. See [my comment](https://github.com/rust-lang/cargo/issues/8923#issuecomment-761847239). Note, there is not really a solution for this yet. Are you able to (eventually)...

I have a couple of thoughts. ### What shell/terminal are you using? It is possible you need to use double backslashes for your path separators. The double backslashes should _not_...

Thank you for the feature request. It seems reasonable to be able to add a start menu and desktop shortcut. These should be added as components and features that can...

I have created and published the [cargo-rustc-cfg](https://crates.io/crates/cargo-rustc-cfg) crate. The `rustc-cfg` crate will eventually be replaced with this one to address this issue.

There are a couple of issues popping up with the cargo-rustc-cfg crate. Cargo is building the project every time for every target because it does not abort the build process...

A [mechanism](https://github.com/rust-lang/cargo/pull/9002) for obtaining the Cargo-based compiler configurations. It will take a while for it to reach stable for Cargo, but this will greatly unify resolution of this issue along...

> Unfortunately, no. There are a lot of different ways to enable static linking of the CRT runtime, and cargo-metadata doesn't give us any of this information. Does the `rustc...

> > How do we determine which CRT installer to include, i.e. version? > > This is... complicated. I believe it depends on which version of the Visual Studio Build...