wixsharp VS api-ms-win-core-path-HACK

I can recommend Wixsharp (https://github.com/oleg-shilo/wixsharp), you no longer have to learn the insane wix xml syntax to create an installer.

Also try wix# (https://github.com/oleg-shilo/wixsharp) - it makes things much easier

Windows: The Microsoft-recommended way is .msi files but, if you're not willing to pay for something like InstallShield or a professional "How to use WiX XML course", making them is going to be painful even with something like WiXSharp, so my advice is to offer a Zip file and an Inno Setup installer. (Which things like Chocolatey can build on)

Wix# is better, but still not as easy, and it depends on .NET, which makes it a hassle to get set up in Wine compared to how, being written in Delphi and using itself as an installer, Inno Setup is practically Rust-like in how easy it is to set up in Wine.

If you really want to bundle a compiler, my advice would be to just use an installer like Inno Setup or NSIS or the WiX Toolset via WixSharp and have it either download or bundle the installer for the compiler.

Speaking of MSI, I'd suggest using Wix# instead of WiX directly.

The functionality in the msilib module is somewhat low-level anyway (it basically just opens the database for you and leaves the arcane incantations required for doing anything as an exercise for the reader) so it probably wouldn't be hugely difficult to replace it with ctypes calling msi.dll directly.

If I were to replace my msilib-based installer, I would migrate to Wix# [1], a fantastic high-level wrapper for WiX that lets you express your installer in a few lines of C# (and then generates the thousands of lines of XML that WiX needs, but you don't need to touch it). I wouldn't have used msilib if I had known about Wix# at the time.

[1] https://github.com/oleg-shilo/wixsharp

Adding that folks should look into using WixSharp especially if there is a need to create a more customizable UI for the installer. The instructions for building the installer is all written in C# including any custom actions required by your installer project.

https://github.com/nalexandru/api-ms-win-core-path-HACK (This is a .dll made by a third-party, Use at your own risk)

api-ms-win-core-hack

You can use https://github.com/nalexandru/api-ms-win-core-path-HACK as a workaround. See relevant StackOverflow link: https://stackoverflow.com/questions/66718131/software-based-on-python-3-9-is-not-working-on-windows-7

Python > 3.9 works just fine on Windows 7 with the api-ms-win-core-path-l1-1-0.dll Wine hack: https://github.com/nalexandru/api-ms-win-core-path-HACK

It's interesting because once Win 10 support drops there will no longer be any x86 Windows path for Python, but there's still a lot of x86 Windows hardware that still works.

I suppose that's more an argument to move to Linux/FreeBSD though on that hardware... I can understand dropping support for something but single breaking changes shouldn't merit it.

But i found what its said to be a patch that lets blender 2.93 run windows 7 ( here is the link: https://github.com/nalexandru/api-ms-win-core-path-HACK/releases/ )

Now it's possible to run installation, although you still need to copy that patch file api-ms-win-core-path-l1-1-0.dll from https://github.com/nalexandru/api-ms-win-core-path-HACK to your AppData\Local\chia-blockchain\app-1.2.6\resources\app.asar.unpacked\daemon folder

I haven't tried Cycles X, but you can still use releases on Windows 7, for now. Use the custom dll implementation to overcome the Python requirement: api-ms-win-core-path-HACK, then for the recent installer, you can disable its OS check with SuperOrca.

2 - Download api-ms-win-core-path-blender-0.3.1.zip from here. (Many thanks to alexandru.naiman for the .dll! (and the OP for the link))

There is a shim that apparently works, but I haven't personally tried so I can't testify to its suitability: https://github.com/nalexandru/api-ms-win-core-path-HACK