Skip to content
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

qtbase: don't require pcre2's default features #42321

Merged

Conversation

nadiaholmquist
Copy link
Contributor

This simply changes the pcre2 dependency of qtbase to not enable the default features. I need to be able to disable them in a project's manifest file, and qtbase not declaring that it doesn't need them is preventing me from doing this.

@nadiaholmquist
Copy link
Contributor Author

@microsoft-github-policy-service agree

@MonicaLiu0311 MonicaLiu0311 added the category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist label Nov 25, 2024
@MonicaLiu0311 MonicaLiu0311 added the info:reviewed Pull Request changes follow basic guidelines label Nov 25, 2024
@BillyONeal BillyONeal merged commit 2d9a19c into microsoft:master Nov 25, 2024
17 checks passed
@BillyONeal
Copy link
Member

Thanks!

@@ -10,7 +11,10 @@
"name": "libb2",
"platform": "!windows"
},
"pcre2",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems kinda odd that qtbase depends on pcre2 but also have a separate feature for it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that seemed weird to me too. I left it as-is because I figured there must have been a reason it was done like that, but if usage of PCRE2 is a feature that is supposed to be disable-able, then it should probably be removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist info:reviewed Pull Request changes follow basic guidelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants