-
Notifications
You must be signed in to change notification settings - Fork 476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
set(OQS_USE_PTHREADS OFF) on MinGW/Cygwin #1695
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks easy enough if there is a container that installs |
This seems to fix the pthread linking issue, but in turn another issue appears (at least for me, running in our Focal Docker container). Running cmake -GNinja -DCMAKE_TOOLCHAIN_FILE=../.CMake/toolchain_windows-amd64.cmake -DOQS_DIST_BUILD=ON -DBUILD_SHARED_LIBS=ON .. && ninja leads to further linking errors, this time seemingly to do with our internal API :( However, this change does make the build pass with |
@SWilson4 If the Focal container is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per discussion. Adding cross-build CI in a separate PR.
I don't think so; I'm using a container based on that one on my local machine, and I installed |
Fixes #1693.
Looks like if cross-compiling from POSIX to Windows, the CMake detect pthreads as available on the host and sets OQS_USE_PTHREADS ON for compilation, which will not work on windows.