[openssl] Support arm64ec

[rohanjain101]

openssl fails on the native arm64ec architecture (for example triplets/community/arm64ec-windows.cmake) because windows/portfile.cmake does not map it to an OpenSSL target:

CMake Error at ports/openssl/windows/portfile.cmake:28 (message):
  Unsupported target architecture: arm64ec

OpenSSL has no ARM64EC configure target (openssl/openssl#16482 was closed as not planned). The usual approach is to build the VC-WIN64-ARM target with /arm64EC and no-asm (see openssl/openssl#30361). This PR does the same:

• VC-WIN64-ARM is the target arm64-windows used before [OpenSSL] Enabling Arm64 assembly on Windows by using clang #34711 switched it to VC-WIN64-CLANGASM-ARM. The vcpkg toolchain already supplies /arm64EC in CFLAGS and CMake's detected /machine:ARM64EC (shared) and /machine:ARM64X (static) in LDFLAGS and ARFLAGS, so no extra flags are needed.
• no-asm is explicit. VC-WIN64-ARM has no asm_arch today, but OpenSSL's AArch64 assembly uses registers that the ARM64EC ABI does not allow (x13, x14, x23, x24, x28, v16-v31), so it must stay off even if the target changes.
• VC-WIN64-ARM defines OPENSSL_SYS_WIN_CORE and links onecore.lib. That only changes OPENSSL_isservice() and OPENSSL_showfatal() (no message box or event log). The resulting DLLs import the usual desktop DLLs (KERNEL32, WS2_32, ADVAPI32, CRYPT32).
• DLL names stay libcrypto-3-arm64.dll and libssl-3-arm64.dll (OpenSSL's -arm64 multilib suffix, as on arm64-windows). Ambiguous Windows ARM DLL naming (arm64 vs arm64ec) causes incompatibility and confusion openssl/openssl#30495 tracks the naming ambiguity upstream.
• OpenSSL 4.0 needed an ARM64EC build fix (Fix windows build failure for arm64ec openssl/openssl#30406). That is relevant for the 4.x update, not for 3.6.5.

x86, x64, arm and arm64 are unchanged.

Tested with MSVC 19.42.34439 (x64-hosted ARM64 cross tools), using overlay triplets that include triplets/community/arm64ec-windows.cmake and chainload a toolchain for that toolset. My local Visual Studio does not have the ARM64EC component.

• Before: vcpkg install openssl:arm64ec-windows fails with the error above.

• After: openssl[core,tools] builds for dynamic arm64ec-windows and for a static-library variant (VCPKG_LIBRARY_LINKAGE static, dynamic CRT). Configure reports VC-WIN64-ARM. There are no post-build warnings, so vcpkg's arm64ec architecture checks pass.

• dumpbin: libcrypto-3-arm64.dll, libssl-3-arm64.dll, legacy.dll and openssl.exe are AMD64 images with ARM64EC hybrid metadata. All import library members and all static library objects are A641 (ARM64EC).

• curl[core,openssl,tool] builds and links against it for both triplets.

• The build machine is x64, so the binaries were not run on ARM64 hardware. We ship a no-asm ARM64EC OpenSSL from an overlay port today; this would let us use the upstream port once our triplets move to native arm64ec.

• Changes comply with the maintainer guide.

• SHA512s are updated for each updated download. (No downloads changed.)

• The "supports" clause reflects platforms that may be fixed by this new version. (No "supports" clause; unchanged.)

• Any fixed CI baseline entries are removed from that file. (None; CI does not test arm64ec.)

• Any patches that are no longer applied are deleted from the port's directory. (None.)

• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.

• Only one version is added to each modified port's versions file.

This change was prepared with help from GitHub Copilot.

[Copilot]

Copilot review overview

🟢 Approval recommended

The architecture mapping, required no-asm option, and version metadata are consistent and narrowly scoped.

Review effort: Balanced
Findings: None

What changed in this PR

Adds native ARM64EC support to the OpenSSL port while preserving existing architecture behavior.

Changes:

• Maps ARM64EC to VC-WIN64-ARM with assembly disabled.
• Increments the OpenSSL port revision and version metadata.

File	Description
ports/​openssl/​windows/​portfile.cmake	Configures ARM64EC builds.
ports/​openssl/​vcpkg.json	Increments the port version.
versions/​baseline.json	Updates the baseline revision.
versions/​o-/​openssl.json	Registers the new port revision.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Billy O'Neal (BillyONeal)]

Thanks!