fix(tauri-cli, tauri-build): copy external binaries only during bundling
Should fix #14602
I'm a bit unsure about moving things from the build script to the tauri-cli, since parts of the bundler were placed deliberately in the build script.
If possible, moving as much as possible from the build script into the tauri-cli could improve code comprehension.
It's not a particularly clean fix, just moving enough out of tauri-build and duplicating some code into tauri-cli.
Package Changes Through 87dd5954afb59e80aab751d68903fd614a353812
There are 3 changes which include tauri-macos-sign with patch, tauri-bundler with patch, tauri-cli with patch
Planned Package Versions
The following package releases are the planned based on the context of changes in this pull request.
| package | current | next |
|---|---|---|
| tauri-macos-sign | 2.3.1 | 2.3.2 |
| tauri-bundler | 2.7.4 | 2.7.5 |
| @tauri-apps/cli | 2.9.5 | 2.9.6 |
| tauri-cli | 2.9.5 | 2.9.6 |
Add another change file through the GitHub UI by following this link.
Read about change files or the docs at github.com/jbolda/covector
If possible, moving as much as possible from the build script into the tauri-cli could improve code comprehension.
The build script does so much shit so that users can use eg cargo run directly so there's only so much we can remove without breaking that.
Is it currently possible to build a fully functional Tauri app without calling tauri build or tauri bundle?
I've tried before and simply running cargo run --bin <app> failed
Ok, so the helloworld example does run with just cargo, never mind then.. Must be something else preventing my other app from running.
This fix has been working for me so far, I guess this would hinge on whether it is expected that bundling only works with tauri-cli.
The only way to break even less workflows would be to copy the binaries as best possible, ignoring errors in tauri-build and then copy again with strict error checking in tauri-cli, but this seems even less pretty.
Thoughts?