Linker error calling certain functions

[kennykerr]

The metadata indicates the name of the DLL that exports the given function, but Rust doesn't yet support DLL imports and expects a LIB file to resolve those imports. If you have the Windows SDK installed, there will usually be a LIB file by the right name that Rust can use but this is not guaranteed. There are a few edge cases where this doesn't quite line up. I considered generating my own LIB files for the windows crate but we have some folks looking into implementing DLL imports for Rust and I'm hopeful that will arrive soon.

One workaround is to generate and provide your own lib files. This process is briefly described here.

Another workaround is to copy the declaration just for the function in question and change the name of the lib to match a suitable lib that does support the function. The msdn docs usually have the correct name of a lib.

[DaLynX]

The second workaround seems easier but unfortunately I do not see how to it. Could you provide some guidance?

[kennykerr]

Hang in there - I'm adding a workaround that should fix this up while we wait for the eventual solution.

[kennykerr]

I applied a workaround - do let me know if that help. #465

[CarePackage17]

I ran into linker issues when trying to use the HasExpandedResources API. Here's my code:

mod bindings {
    ::windows::include_bindings!();
}

use bindings::{
    windows::win32::game_mode::*,
};

fn main() {
    unsafe {
        let mut game_mode: i32 = 0;
        let error = HasExpandedResources(&mut game_mode);
        if error.is_ok() {
            println!("Running in game mode: {}", game_mode != 0);
        }
    }

Linker says:

...
= note: LINK : fatal error LNK1181: cannot open input file 'api-ms-win-gaming-expandedresources-l1-1-0.lib'

The docs for this function say to link against WindowsApp.lib though, so not sure why that API set ends up here...

[kennykerr]

Thanks for the repro - I'll update the workaround to cover this.

[kennykerr]

A more comprehensive workaround is now in place to deal with the linker issue. You should now be able to use this function without issue.