Closed Massimiliano-solutiontech closed 1 year ago
cool. tarball to repro?
Works for me under stable-x86_64-pc-windows-gnu by running cargo build
in test-app/src-tauri
, but I see both the requestedPrivileges
sample manifest and the icon in the resulting executable. Notably, the sample manifest does not include an icon (and you haven't added it there), so I'm assuming the linker merges these for me.
I even see in target/debug/build/test-app-2c1454acc47ad2b2/output
:
cargo:rustc-link-arg-bins=T:\test-app\src-tauri\target\debug\build\test-app-2c1454acc47ad2b2\out/libresource.a
cargo:rustc-link-arg-bins=T:\test-app\src-tauri\target\debug\build\test-app-2c1454acc47ad2b2\out/libtest-app-manifest.a
and a corresponding https://github.com/tauri-apps/winres/blob/db468ecc70ba7f47b01e7d289c12cd7ca3b381f6/lib.rs#L641 (I think it's corresponding, the layout is hell).
I'm therefore concluding that (a) LINK.EXE cannot deal with multiple manifests, (b) r-e-r works as expected here, and (c) you should either find a way to give the tauri build system a manifest instead of using r-e-r or disable its own manifest injection.
I created both the files
app-name-manifest.rc
andapp-name.exe.manifest
in the root of Rust./src-tauri
when I launchnpm run tauri build
I get the following error