oqsprovider can also be build on/for Windows using Microsoft Visual
Studio for C (MSVC) or cygwin. For the latter, please check the
notes for Unix.
OpenSSL (>=3.0.0) is not yet generally available under Windows. It is therefore sensible to build it from scratch.
For that, please follow the instructions here. A complete scripted setup is available in the CI tooling for oqs-provider.
Instructions for building liboqs from source is available
here.
oqsprovider is best built on Windows when git access, cmake, ninja and
a C compiler are present, e.g., as in MS Visual Studio 2022.
A standard cmake build sequence can be used (assuming prerequisites are installed)
to build in/install from directory build:
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS="/wd5105" -GNinja -S . -B build && cd build && ninja && ninja install
The specific CMAKE_C_FLAGS silence some overly strict warning messages and
the specific reference to the build type ensures a shared library with
release symbols, suitable for use with a release-symbol openssl build
is created.
If openssl and/or liboqs have not been installed to system standard locations
use the cmake defines "-DOPENSSL_ROOT_DIR" and/or "-Dliboqs_DIR" to utilize
those, e.g., like this:
cmake -DOPENSSL_ROOT_DIR=c:\opt\openssl3 -Dliboqs_DIR=c:\liboqs -S . -B build && cmake --build build && cmake --install build
Further configuration options are documented here.
Standard ctest can be used to validate correct operation in build directory build, e.g.:
ctest -V --test-dir build
Packaging the resultant .DLL is not yet implemented. Suggestions which package manager to use are welcome.