To build portable pre-compiled packages and Windows installers for major platforms.

Motivation & Context

The TaurusTLS-Developers team has been supplying the Delphi, Free Pascal, and C++Builder developer communities with pre-compiled OpenSSL binaries through automated CI/CD builds at TaurusTLS-Developers/OpenSSL-Distribution tracking upstream releases.

We fully embrace and welcome the official OpenSSL binary distribution provided directly by the OpenSSL project. However, our consumers have specific platform requirements: they actively rely on pre-compiled Windows binaries for x86, x64, and ARM64EC.

The TaurusTLS team would like to assist you in integrating x86 and ARM64EC support into the official installer.

Why ARM64EC and x86?

• ARM64EC (Windows on Arm): While pure ARM64 works for standalone apps, toolchains like Embarcadero Delphi target the ARM64EC ABI to run natively on Windows on Arm devices while maintaining x64 interoperability.
• x86 (32-bit): 32-bit targets remain heavily used for active development, legacy integration, and debugging across the Delphi, Free Pascal, and C++Builder developer communities.

What we have working

In our pipeline, we have already resolved the toolchain details for these targets:

1. ARM64EC Target Configuration: Custom target handling /arm64EC, architecture-specific flags, warning suppressions, and correct archiver/linker machine types (/MACHINE:ARM64EC).
2. HybridCRT Linkage: Statically linking the VC runtime (/MT) while dynamically linking the Universal CRT (ucrt.lib), eliminating external vcruntime140.dll dependencies across all Windows architectures.
3. Multi-Architecture Packaging: Automated staging and packaging logic for multi-arch distributions.

What is the best path to contribute?

We would like to contribute this work upstream so consumers can get these platforms directly through the official trusted channel.

What is the preferred approach for the team? We can:

• Open a PR with our target configurations and build script adjustments.
• Help adapt the existing WiX/MSI packaging setup to include ARM64EC and x86 payloads.
• Assist with testing on GitHub-hosted windows-11-arm runners.

Begin by reading the existing target configurations and build scripts, then inspect the WiX/MSI packaging setup and current automated CI/CD pipeline. Done means the project has an agreed upstream path for x86 and ARM64EC payloads, with packaging tested on the mentioned Windows ARM runner.