When building a Tauri project, can certain downloaded items specify a local file path through configuration or environment variables?

[xb284524239]

When I run the command npx tauri build, the console shows that a zip file is being downloaded: Downloading https://github.com/wixtoolset/wix3/releases/download/wix3141rtm/wix314-binaries.zip, and this download process takes a long time.

If I copy the wix314-binaries.zip file from another computer to my computer, is there a way to specify the local path of this file through configuration or environment variables so that when executing the npx tauri build command, it doesn't need to download it from the network?

[FabianLars]

Nope, not yet at least. If you want to download the files yourself you have to move them to the required locations as well, example: #7338 (comment)

Alternatively, if it's just the github links we use being problematic you can also specify different download urls via one of these env vars:

• TAURI_BUNDLER_TOOLS_GITHUB_MIRROR - Specify a GitHub mirror to download files and tools used by tauri bundler.
• TAURI_BUNDLER_TOOLS_GITHUB_MIRROR_TEMPLATE - Specify a GitHub mirror template to download files and tools used by tauri bundler, for example: https://mirror.example.com/<owner>/<repo>/releases/download/<version>/<asset>.

Copied from https://github.com/tauri-apps/tauri/blob/dev/crates/tauri-cli/ENVIRONMENT_VARIABLES.md

[xb284524239]

Thanks!

[xb284524239]

According to the source code of tauri/crates/tauri-bundler/src/bundle/windows/nsis/mod.rs and tauri/crates/tauri-bundler/src/bundle/windows/msi/mod.rs, the following links are the latest download address.

1. Download https://github.com/wixtoolset/wix3/releases/download/wix3141rtm/wix314-binaries.zip and extract to %localappdata%/tauri/WixTools314.
2. Download https://github.com/tauri-apps/binary-releases/releases/download/nsis-3/nsis-3.zip and extract to %localappdata%/tauri/NSIS.
3. Download https://github.com/tauri-apps/nsis-tauri-utils/releases/download/nsis_tauri_utils-v0.5.1/nsis_tauri_utils.dll and put it into %localappdata%/tauri/NSIS/Plugins/x86-unicode/additional/nsis_tauri_utils.dll.

By the way, it would be great if, in addition to telling us the URLs of the files that need to be downloaded, Tauri could also inform us of the local path where the files should be unzipped or stored in its output logs during the build process. That way, we wouldn't have to look through Tauri's source code.