LibreSSL Portable itself. This includes the build scaffold and compatibility layer that builds portable LibreSSL from the OpenBSD source code. Pull requests or patches sent to tech@openbsd.org are welcome.
Visual studio has an option to use Clang-CL as a backend - it's supposed to behave like 'cl.exe' but is clang and llvm.
with libressl source in a directory, from that directory... In order to enable it - using the visual studio installer, under Modify 'Individual components` search for 'clang' and select all options...
mkdir build
cd build
cmake -T ClangCL ..
and build resulting libressl.sln ( can either use cmake --build . or load the project in visual studio)
and then a ton of error in the test projects are generated... for example:
lld-link : error : duplicate symbol: posix_perror [M:\javascript\vfs\native\src\sack\libressl\3.9.2\build\tests\aeadtest.vcxproj]
>>> defined at M:\javascript\vfs\native\src\sack\libressl\3.9.2\crypto\compat\posix_win.c:25
>>> M:\javascript\vfs\native\src\sack\libressl\3.9.2\build\crypto\compat_obj.dir\Debug\posix_win.obj
>>> defined at crypto.lib(posix_win.obj)
Also get a bunch of warnings... the clang-cl compiler is using clang warnings instead of the C4496 sort of warning... for example:
"C4996" # The POSIX name for this item is deprecated.
# Instead, use the ISO C and C++ conformant name
This fixes additional warnings... (for building the library anyway)
The above is a 32 bit build... enabling -A x64 so assembly builds fails for a different reason... (Pretty sure this is a MS issue, since the /W3 that's getting added is from 'masm.target' build rule.) cmake -T ClangCL -A x64 ..
(This last one I was just trying to figure out exactly what was causing a compile error; if I disable assembly I guess I can get past this, CMake also has code in it to add /W3 erroneously to the C,C++ compiler flags... though I'm not sure if that IS an issue of if it's just this ml64.exe that's puking )
Edit: This last one is apparently caused by me.... I had a warning disable from 3.8.0
Visual studio has an option to use Clang-CL as a backend - it's supposed to behave like 'cl.exe' but is clang and llvm.
with libressl source in a directory, from that directory... In order to enable it - using the visual studio installer, under Modify 'Individual components` search for 'clang' and select all options...
and build resulting libressl.sln ( can either use
cmake --build .
or load the project in visual studio) and then a ton of error in the test projects are generated... for example:Also get a bunch of warnings... the clang-cl compiler is using clang warnings instead of the C4496 sort of warning... for example:
This fixes additional warnings... (for building the library anyway)
(disregard below...)
The above is a 32 bit build... enabling
-A x64
so assembly builds fails for a different reason... (Pretty sure this is a MS issue, since the /W3 that's getting added is from 'masm.target' build rule.)cmake -T ClangCL -A x64 ..
(This last one I was just trying to figure out exactly what was causing a compile error; if I disable assembly I guess I can get past this, CMake also has code in it to add /W3 erroneously to the C,C++ compiler flags... though I'm not sure if that IS an issue of if it's just this
ml64.exe
that's puking )Edit: This last one is apparently caused by me.... I had a warning disable from 3.8.0
with that, then the assembly fails with /W3 (so disregard after horizontal bar above)