-
Notifications
You must be signed in to change notification settings - Fork 7.4k
[xmlsec] Update to 1.3.7 #43808
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
Merged
Merged
[xmlsec] Update to 1.3.7 #43808
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
b40b309
[xmlsec] Update to 1.3.7
metsma 3bcfa1c
Add WIN32_LEAN_AND_MEAN define like upstream
metsma 7721a6c
XMLSEC_DL_LIBLTDL is internal flag
metsma 03afba2
Upstream deprecated MD5 and RIPEMD160 algos
metsma 0edbf59
Sync pkg-config flags with cmake flags
metsma 682ce30
Use same configuration as upstream
metsma 9b3f64d
Add version
metsma File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
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.
Why isn't this OpenSSL stuff coming from
find_package? (I'm not saying this wrong per se, I just want to make sure I have an understanding of what's going on here before reviewing it incorrectly 😅)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.
I am really not that familiar with pkg-config. Is there some sort of dependency system?
Upstream hardcodes also flags to pkg-config files.
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.
The pkg-config dependency system is the
RequiresandRequires.privatefields.(Isn't it possible to use
vcpkg-makeinstead of maintaining a vcpkg CMakeLists.txt?)Uh oh!
There was an error while loading. Please reload this page.
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.
I just noticed that pkg-config files were out of sync with cmake parameters and improve current situation.
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.
The make handling has gotten a LOT better over time; if we can use upstream's build system we should if at all possible though. I don't think we should block someone trying to do a 'simple update' on changing the build system but this seems to already be doing a lot of surgery.
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.
I guess, I'm not sure it does improve the current situation? This can't seem to make up its mind about whether it wants OpenSSL::OpenSSL or to hard code
-lcryptoand friends. It seems like that can't be correct.I'm all for 'code that isn't green doesn't necessarily have to change even if it does unfortunate things' but you made this code green :)
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.
I'm not sure I follow. Here's an example showing that the pkg-config vs cmake files are missing the compile definitions used. If this change is distracting, I can revert to the previous setup.
Current:
New:
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.
Maybe it is easier dump the pkg-config changes to get the version pump accepted?
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.
OK, I think you've shown that the output at least isn't worse than what was here before.
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.
(But I still think the correct thing to do is to
get_target_propertiesor similar what the real flags should be out ofOpenSSL::OpenSSLrather than assuming it will be exactly-lcrypto)