Files
dxdesigner-part-replacement/packaging/SELF-EXTRACTING-RELEASE.md
阿白叔 1340f6c233
Core regression / Python core and release configuration (push) Successful in 18s
Core regression / JavaScript syntax (push) Successful in 3s
build: stage immutable release files without duplicate copies
2026-11-04 15:47:21 +08:00

2.5 KiB

Windows self-extracting release

Build the complete application with Build-DxPartReplace.ps1 first. The spec now fails if the installed DSH package, reporter configuration or Node executable is missing. Keep the entire installed integration/dsh/node_modules tree, including lazy runtime dependencies.

Use the official 7-Zip 26.05 x64 tools from:

Extract the installer with an existing 7-Zip tool into a build-only directory. No machine-wide installation is needed. Use that directory's 7z.exe, 7z.dll, 7z.sfx and License.txt. The standard 7z.sfx opens a destination selector and extracts to a persistent directory. It is not the install-to-temp SFX module; it takes no installer configuration and does not auto-launch or delete the extracted application.

python tools/build_self_extracting_release.py --source-dir dist/DxPartReplace --output-dir G:/dx-release-1.2.2 --version 1.2.2 --seven-zip build/7zip-2605/full/7z.exe --sfx-stub build/7zip-2605/full/7z.sfx --license build/7zip-2605/full/License.txt

Use a fresh output directory and keep the completed build input unchanged during packaging. The tool rejects an existing directory, overlapping input/output paths and an application input containing data. It stages the complete input using same-volume hardlinks (copying when links are unavailable), includes the 7-Zip license, produces independent EXE + ZIP archives, and writes artifact and per-file SHA256 hashes. LZMA2 level 3 and bounded solid blocks keep decoding memory modest; tiny files still incur filesystem costs, so do not promise a fixed speedup across machines.

Before publishing, run the self-extracting EXE itself with -y -o<fresh directory>, compare every resulting file and every ZIP member against the manifest, and run tools/verify_packaged_runtime.py and Qt/DSH UI acceptance on that extracted EXE. Neither merely listing the archive nor the source UI tests replaces this check.

The optional Windows integration test exercises the real SFX with Chinese/spaced paths and empty/binary files. Set DX_SFX_TEST_TOOLS to the official tools directory and run python -m pytest tests/packaging/test_self_extracting_release.py. Linux CI runs the portable output-protection checks and explicitly skips the Windows integration.