#How to customize the build logic of a tauri app?

5 messages · Page 1 of 1 (latest)

glad pebble
#

For example, I want to pack different files based on the target CPU architecture. Or I want to use a non NSIS installer for bundling my app (e.g. InnoSetup). Or generate a release manifest using my own schema.

What solution does the tauri offer for such a requirement?

lean quail
wicked sorrel
#

For example, I want to pack different files based on the target CPU architecture.
(assuming you mean with tauri's default bundler): https://github.com/tauri-apps/tauri/issues/8501 (until then you could use the --config flag)

For the rest there's not much tauri can offer you. just take the exe like the message before me said and do your own thing.

Or generate a release manifest using my own schema.
not sure what you mean with that tbh

edit: potentially interesting as well https://github.com/tauri-apps/tauri/issues/12937

glad pebble
#

@lean quail @wicked sorrel You're talking about particular libraries and tools. But all of my examples are examples. The question is - how to perform ANY kind of a project specific build logic developing a tauri app

For example, in Electron there's such things Like Electron Forge which allow you to provide your own maker and publishers. In java development there's Gradle. In frontend development there are buldlers and their plugin system.

But what about tauri?

lean quail
#

Tauri doesn't provide much for packaging languages, but there is another solution, which is to run npm run tauri build and then move app.exe to your InnoSetup resource directory for packaging.