-
Notifications
You must be signed in to change notification settings - Fork 13.4k
compiler panicked - tauri #111855
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
Comments
this morning it works... made a few changes to configs. Maybe a tauri compile crashes if there's not a proper distDir? If anyone ever looks at this, you can see the changes from crashing to working with git diff c7f6b00114f5bc85503fdd2b7d9ce6b84d210854 |
I looked into this shortly after you reported it. This ICE looks concerning to me; it is from a checked conversion of a But I can't reproduce it. I'm on
I run
And no ICE. Is there something else I need to do? I have no idea what tauri is. |
info Tauri is a toolkit for hosting a web app frontend in a rust desktop app, or mobile app. I'm just getting started with it. FWIW I also have some android compile targets installed, though I don't know that they would affect anything here. The way I'm setting up my build env is with When this tauri project compiles it apparently looks at the tauri.conf.json file during the process. If that is incorrect it has problems. The one from commit c7f6b00114f5bc85503fdd2b7d9ce6b84d210854 is I think incorrect. another try Just gave it another try, checking out the c7f6b00114f5bc85503fdd2b7d9ce6b84d210854 commit on my laptop. I'm calling Mostly |
I don't use nix. Running I'm also not seeing a hang at the last step of the build. So I think there's something different about my build environment. I see a lot of stuff in the file that describes the flake, things like |
I fixed this in #113542 and forgot to link this issue at the time. |
Trying to compile a tauri project. Worked ok before but not now after trying to get tauri-mobile working.
Code
bburdette/zknotes@c7f6b00
Error output
The text was updated successfully, but these errors were encountered: