Thank you for creating great crates. I have some questions.

I want to customize CreateCoreWebView2EnvironmentOptions. And I implemented feature to create environment like the following. This is customizing language through CreateCoreWebView2EnvironmentOptions.

CreateCoreWebView2EnvironmentCompletedHandler::wait_for_async_operation(
  Box::new(move |environmentcreatedhandler| unsafe {
    let options = {
      let options: ICoreWebView2EnvironmentOptions =
        CoreWebView2EnvironmentOptions::default().into();

      // Setting user's system language
      let lcid = Globalization::GetUserDefaultUILanguage();
      let mut lang = [0; MAX_LOCALE_NAME as usize];
      Globalization::LCIDToLocaleName(
        lcid as u32,
        &mut lang,
        Globalization::LOCALE_ALLOW_NEUTRAL_NAMES,
      );
      options
        .SetLanguage(PCWSTR(lang.as_ptr()))
        .map_err(webview2_com::Error::WindowsError)?;
      options
    };

    // remove "mini menu" - See https://github.com/tauri-apps/wry/issues/535
    let _ = options.SetAdditionalBrowserArguments("--disable-features=msWebOOUI,msPdfOOUI");
    CreateCoreWebView2EnvironmentWithOptions(
      PCWSTR::default(),
      PCWSTR::default(),
      options,
      environmentcreatedhandler,
    )
    .map_err(webview2_com::Error::WindowsError)
  }),
  Box::new(move |error_code, environment| {
    error_code?;
    tx.send(environment.ok_or_else(|| windows::core::Error::from(E_POINTER)))
      .expect("send over mpsc channel");
    Ok(())
  }),
)?;

And call environment.CreateCoreWebView2Controller then get CoreWebView2 and navigate webview2. But My custom language is not reflected.

To resolve this problem, I think webview2 need to call EnsureCoreWebView2Async(CoreWebView2Environment, CoreWebView2ControllerOptions) or set environment to CreationProperties like written in here. Or does webview2-com crate reflect environment implecitly?

Thank you for reading my issue.

I have a very simple application based on wry that does little more than displaying a website in a window right now. A mandatory part of my "walking skeleton" is a fully functional build pipeline and this is where I have been stuck for 2 days now.

Here's what I do to build the Windows version of the application:

1. I use a shared Windows runner provided by GitLab, which comes with this default configuration: https://gitlab.com/gitlab-org/ci-cd/shared-runners/images/gcp/windows-containers/blob/main/cookbooks/preinstalled-software/README.md
2. In the CI script, I use chocolatey to install llvm and rust
3. I run cargo build --release

This all sounds pretty vanilla and works fine until this happens:

Compiling webview2-com-sys v0.13.0
error: failed to run custom build command for `webview2-com-sys v0.13.0`
Caused by:
  process didn't exit successfully: `C:\GitLab-Runner\builds\[redacted]\target\release\build\webview2-com-sys-d5a6ffdd174e101d\build-script-build` (exit code: 1)
  --- stdout
  cargo:rustc-link-search=native=C:\GitLab-Runner\builds\[redacted]\target\release\build\webview2-com-sys-3ac9dd9042e7e7c5\out\x64
  --- stderr
  Copy from "C:\\Users\\gitlab_runner\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\webview2-com-sys-0.13.0\\arm64\\WebView2Loader.dll" -> "C:\\GitLab-Runner\\builds\\[redacted]\\target\\release\\build\\webview2-com-sys-3ac9dd9042e7e7c5\\out\\arm64\\WebView2Loader.dll"
  Copy from "C:\\Users\\gitlab_runner\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\webview2-com-sys-0.13.0\\arm64\\WebView2Loader.dll.lib" -> "C:\\GitLab-Runner\\builds\\[redacted]\\target\\release\\build\\webview2-com-sys-3ac9dd9042e7e7c5\\out\\arm64\\WebView2Loader.dll.lib"
  Copy from "C:\\Users\\gitlab_runner\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\webview2-com-sys-0.13.0\\arm64\\WebView2LoaderStatic.lib" -> "C:\\GitLab-Runner\\builds\\[redacted]\\target\\release\\build\\webview2-com-sys-3ac9dd9042e7e7c5\\out\\arm64\\WebView2LoaderStatic.lib"
  Copy from "C:\\Users\\gitlab_runner\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\webview2-com-sys-0.13.0\\x64\\WebView2Loader.dll" -> "C:\\GitLab-Runner\\builds\\[redacted]\\target\\release\\build\\webview2-com-sys-3ac9dd9042e7e7c5\\out\\x64\\WebView2Loader.dll"
  Copy from "C:\\Users\\gitlab_runner\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\webview2-com-sys-0.13.0\\x64\\WebView2Loader.dll.lib" -> "C:\\GitLab-Runner\\builds\\[redacted]\\target\\release\\build\\webview2-com-sys-3ac9dd9042e7e7c5\\out\\x64\\WebView2Loader.dll.lib"
  Copy from "C:\\Users\\gitlab_runner\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\webview2-com-sys-0.13.0\\x64\\WebView2LoaderStatic.lib" -> "C:\\GitLab-Runner\\builds\\[redacted]\\target\\release\\build\\webview2-com-sys-3ac9dd9042e7e7c5\\out\\x64\\WebView2LoaderStatic.lib"
  Copy from "C:\\Users\\gitlab_runner\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\webview2-com-sys-0.13.0\\x86\\WebView2Loader.dll" -> "C:\\GitLab-Runner\\builds\\[redacted]\\target\\release\\build\\webview2-com-sys-3ac9dd9042e7e7c5\\out\\x86\\WebView2Loader.dll"
  Copy from "C:\\Users\\gitlab_runner\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\webview2-com-sys-0.13.0\\x86\\WebView2Loader.dll.lib" -> "C:\\GitLab-Runner\\builds\\[redacted]\\target\\release\\build\\webview2-com-sys-3ac9dd9042e7e7c5\\out\\x86\\WebView2Loader.dll.lib"
  Copy from "C:\\Users\\gitlab_runner\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\webview2-com-sys-0.13.0\\x86\\WebView2LoaderStatic.lib" -> "C:\\GitLab-Runner\\builds\\[redacted]\\target\\release\\build\\webview2-com-sys-3ac9dd9042e7e7c5\\out\\x86\\WebView2LoaderStatic.lib"
  Error: Io(Error { kind: NotFound, message: "program not found" })

This seems to be specific to the build environment. When I run the same steps on a regular Windows 10 machine, everything works out fine.

What am I missing? Do I have to prepare any files by hand? Have I overlooked a critical piece of configuration?

Any help would be greatly appreciated!

Hello! I was trying to compile wry with cargo cross from wsl2 to windows, and it fails on building webview2-com-sys due to this error:

error: could not find native static libraryWebView2LoaderStatic, perhaps an -L flag is missing?

When I looked at the build.rs script for that package, it seems to use the cfg attributes to test for windows or not windows. Unfortunately it doesn't play well with cross compiling (as explained here: https://kazlauskas.me/entries/writing-proper-buildrs-scripts).

Any thoughts?

On Windows, sometimes the Nuget configuration is not set so the CLI fails without a source to load a packag. We're seeing this issue oftenly at Tauri, and even had to start our FAQ with a way to troubleshoot this issue. I believe this happened to almost 10 users.

This PR changes the build script to exit if the nuget installation fails, showing the CLI output to help users find the problem.

Cross-compilation needs to use mono to run the nuget.exe CLI tool and download the WebView2 SDK to the output directory. Now that there's support for that, the binaries no longer need to be committed to the repo, the build script can do it every time, as long as mono is installed. If mono is not installed, the build script will show an error (with panic!) indicating that it needs mono to run nuget.exe.

The *-pc-windows-msvc targets support linking against the WebView2LoaderStatic.lib static library, but the *-pc-windows-gnu targets used in most cross-compilation scenarios need to link to the WebView2Loader.dll DLL with the WebView2Loader.dll.lib import library. To get this working, I had to patch the generated bindings and replace the #[link(...)] attributes with different versions wrapped in #[cfg_attr(...)] for target = "msvc" and not(target = "msvc").

Now that every host system is expected to run nuget.exe, there's no more reason to copy the binaries to the .windows/ directory. Adding the path from the NuGet package installation under target/ to cargo:rustc-link-search in the build script automatically adds it to the DLL search path when you run a test or example through cargo. This should also apply to consumers of webview2-com.