New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[shell] Can't build 2.0.0-beta3 for Windows 32-Bit #1046
Comments
This is the same as Byron/open-rs#91 (comment), could you share the repo or a minimal repro where this issue happens as I am unable to reproduce. |
Yes, I also just found this issue and it mentioned exactly the same.
Unfortunately I can't share I can't share the main application repo. But as I said it's reproducible using the current Tauri beta. I'll try to list the steps for reproduction (see my
I'll try in another machine/setup and test if it behaves the same. |
Thank you, I think I have found the problem. Will open a PR upstream. |
Opened a PR here: Byron/open-rs#93 you can try the fix by adding the following patch inside Cargo.toml: [patch.crates-io]
open = { git = "https://github.com/tauri-apps/amrbashir", branch = "fix/shell-execute-w-link" } then do |
I can confirm that it's fixed in your branch. Looking forward to your PR getting merged upstream. Thanks for the fast fix! |
The PR has been merged and released, you can remove the patch and just do |
In our project (Windows 32-Bit support needed,
i686-pc-windows-msvc
) we updated from2.0.0-beta0
to2.0.0-beta3
(both versions2.0.0-beta1
and2.0.0-beta2
did not compile in the combination with other Tauri deps). 64-Bitx86_64-pc-windows-msvc
however builds just fine.The build process aborts with the MSVC linker giving this error message (unresolved external symbol) when trying to link
ShellExecuteW
forlibopen
:I noticed that with #1021 the dependency of crate
open
was raised from major version 4 to 5. Maybe this is related. I'm unsure whether this is an issue of the shell plugin or with the open crate.This is reproducible with a fresh Tauri2-beta.
The text was updated successfully, but these errors were encountered: