Ability to prevent linking of dlls

[wmmc88]

Suggestion

I wanted to be able to only import NTSTATUS values from this crate, but doing so pulls in many dlls. The way in which the dlls are imported actually breaks my build because it forces some of my own ffi bindings to try to link against ntdll instead of my own dlls.

[kennykerr]

That's not something the windows or windows-sys crates support.

You could experiment with setting windows_raw_dylib which would prevent the lib crates from being included.

windows-rs/.cargo/config.toml

Line 4 in 101467c

# "--cfg", "windows_raw_dylib",

Alternatively, you might want to consider using the windows-bindgen crate to generate just the constants you need.

[wmmc88]

enabling windows_raw_dylib does prevent the linking issue! When might windows_raw_dylib become the default?

[kennykerr]

raw-dylib is finally stabilized so it's just a matter of time before the MSRV can handle it. Not sure yet when that will be.

[wmmc88]

Im not sure what you mean by "the MSRV can handle it". According to rust-lang/rust#58713, it looks like the feature was stabilized for 1.65, so isn't it just a matter of when you decide to increase the msrv to >= 1.65? What is the policy for increasing msrv in windows-rs crates?

Aside: It looks like the msrvs listed in the docs don't match with the ones defined in the cargo.tomls

[kennykerr]

I just bumped it to 1.56.0 - it will likely be a while until it gets bumped to 1.65, but your scenario is a little different so I wouldn't worry about that.

Yes, I need to update the docs.

[kennykerr]

I have updated the docs at https://kennykerr.ca/