-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[feat] firendly error output when make nsis bundle on linux but got (os error 2) #9221
Comments
The issue you linked was fixed before the first nsis release so i doubt it's related. Is the output you posted with the Also please post the output of the Lastly, do you have a minimal reproduction for this, or is your project public? |
Yes I used
Here is minimal produce code repository: https://github.com/LemonNekoGH/os-error-2-minimal This error can be fixed by change product name to lowercase. |
I also have the same problem by running: Error failed to bundle project: Change product name to lowercase solved it. |
This should be fixed (by accident) in the latest beta cli version (beta.13). Can someone confirm this? Edit: Correction, this will be fixed in an upcoming v2 release. I still had the CLI from this pr installed in my test... The implementation won't work for the v1 branch so i'll try to find another fix. |
Describe the problem
I am using
tauri cli 1.5.11
, i always getError failed to bundle project: No such file or directory (os error 2)
when i build nsis bundle on linux, i don't know why, then i found a issue #6743 about this error, so i think my tauri version is too low, but after i upgraded to2.0.0-beta.9
, this error still exist.I am so confused, so i debug the tauri cli line by line, i found my binary file name is not nsis needs, just because my
package.productionName
isBDSM
but nsis needsbdsm
, the error occoured at:tauri/tooling/bundler/src/bundle/windows/nsis.rs
Line 636 in d349558
Here is the error log:
Describe the solution you'd like
I think, can we provide which file name caused
No such file or directory
like this:Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: