HaloSPV3/HXE

Publish both x86 and x64 apps

BinToss opened this issue · 1 comments

https://twitter.com/VoidsShadow/status/1450000709890424834

Hear the lament of one who must maintain a single-file, self-extracting installer that has a 64-bit-only feature and must run on both 32-bit and 64-bit platforms.

https://twitter.com/VoidsShadow/status/1450401081809416198

I couldn't find a way to create an 'Any CPU' app with net5.0+ tools despite implications in its source code and documentation, so I'll have to split 64-bit-only features to a separate application or library that is stored in and later extracted from a 32-bit SPV3 Installer.

😠

Miris Wisdom

why not have the x64 project straight in the HXE repo then?
./src
./doc
./x64

BinToss

Why didn't I think of that? Better yet, why didn't I consider using a Build and Release matrix to avoid the need for a new project?
In that case, the apps could be released together with their filenames having CPU-arch suffixes.
HaloSPV3/SPV3-Installer (todo) would still have to publish for x86 with HXE-x64.exe embedded as a resource that hopefully won't be bagged and tagged by AV software.

Miris Wisdom

ah, yer, you could set up build configs for x64 for per-arch executables
and ehhhh, embedded executables are certainly a gamble