xmlsec: fix header conflicts between OpenSSL and Windows #26622
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes to recipe: xmlsec/1.3.6
Motivation
fixes #26621
Details
Set the define
WIN32_LEAN_AND_MEANwhen the compiler is mingw . TheWIN32_LEAN_AND_MEANdefine is used in Windows to exclude some of the less frequently used APIs from the Windows headers. This can help prevents the inclusion of some headers like cryptography, among others that can help to fix header conflicts with openssl.This is based on the defines used on msvc makefile in the project:
https://github.com/lsh123/xmlsec/blob/f48168188a9d0ecda4a19b3f5586860b00d81b69/win32/Makefile.msvc#L365-L375