Currently all our builds are targeting pure MSVC / MinGW with GCC. No builds are targeting LLVM.
There is VC-WIN64-CLANGASM-ARM configuration in OpenSSL since 3.1, where it supports ASM compile using clang-cl, and C code compile using MSVC cl and link the final executable together.
Another thing is VC-CLANG-WIN64-CLANGASM-ARM, also available since 3.1, support whole program compile and link using clang-cl.
Things which should be tried on each branch:
Number
Configuration
Toolchain
CC
ASM
perlasm scheme
1
VC-CLANG-WIN32
MSVC
clang-cl
<none>
N/A
2
nasm
win32n
3
VC-CLANG-WIN64A
<none>
N/A
4
nasm
nasm
5
VC-CLANG-WIN64-ARM
<none>
N/A
6
VC-CLANG-WIN64-CLANGASM-ARM
clang-cl
win64
7
VC-WIN32-CLANGASM
cl
clang-cl
coff
8
VC-WIN64-CLANGASMA
mingw64
9
VC-WIN64-CLANGASM-ARM
win64
10
mingw
MinGW
clang
<none>
N/A
11
clang
coff
12
mingw64
<none>
N/A
13
clang
mingw64
14
mingwarm64
<none>
N/A
15
clang
win64
Notes about above toolchains:
clang-cl with MSVC toolchain should be built using official LLVM distribution
VC-CLANG-* configuration may be some extension of my project
Currently all our builds are targeting pure MSVC / MinGW with GCC. No builds are targeting LLVM.
There is
VC-WIN64-CLANGASM-ARM
configuration in OpenSSL since 3.1, where it supports ASM compile usingclang-cl
, and C code compile using MSVCcl
and link the final executable together. Another thing isVC-CLANG-WIN64-CLANGASM-ARM
, also available since 3.1, support whole program compile and link usingclang-cl
.Things which should be tried on each branch:
Notes about above toolchains:
clang-cl
with MSVC toolchain should be built using official LLVM distributionVC-CLANG-*
configuration may be some extension of my projectclang
with MinGW should be built using llvm-mingw from mstorsjomingwarm64
exists as MSYS2 downstream patch, so we just use the configuration name.3.2:
Other branches should be same as 3.2 but there is possibility that ASM can't be supported