Single binary and documenting how #13160
-
|
Hello, I "struggled" on "where" / "how" to build a single production (not dev) binary until I figured out it was simply in the The documentation doesn't seem to really specify this (unless I misread which is totally possible). It mostly indicates on how to distribute ( I'm in a case where, for the moment, the application I'm working on is only for me. So, I'm only starting with "I work for me and not the others" (I can totally understand it isn't the general philosophy). If I'm not wrong, I would like to know why (something as "simple") as this isn't mentioned in the documentation ? I think (I may be wrong) it would be useful for some people (?) Thank you very much in advance for any help |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Because those binaries (except for windows i guess) are somewhat for edge case uses only in the flow of tauri build. Also, Tauri is just a normal rust project in that context as you noticed. We could of course add documentation on this (to at least warn users that those binaries are not distributable instead of just assuming knowledge realistically nobody has), but i consider this something we'll have to rely on community contributions at the moment. |
Beta Was this translation helpful? Give feedback.
-
Indeed, I completely agree
Thank you I undestand Thank you for your time and help |
Beta Was this translation helpful? Give feedback.
Because those binaries (except for windows i guess) are somewhat for edge case uses only in the flow of tauri build. Also, Tauri is just a normal rust project in that context as you noticed.
We could of course add documentation on this (to at least warn users that those binaries are not distributable instead of just assuming knowledge realistically nobody has), but i consider this something we'll have to rely on community contributions at the moment.