Skip to content

ext/intl: don't always enforce c++17 #14192

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

Closed
wants to merge 1 commit into from

Conversation

jpalus
Copy link
Contributor

@jpalus jpalus commented May 10, 2024

the intention of this condition was to check if build is done against icu >= 74 while in practice it's a condition in the form of test STRING which in turn is equivalent to test -n STRING that checks if passed string is not empty. condition is always satisfied and hence c++17 is also always required.

strip test part and invoke pkg-config directly in condition.

the intention of this condition was to check if build is done against icu >= 74
while in practice it's a condition in the form of `test STRING` which in turn is
equivalent to `test -n STRING` that checks if passed string is not empty.
condition is always satisfied and hence c++17 is also always required.

strip `test` part and invoke `pkg-config` directly in condition.
@jpalus
Copy link
Contributor Author

jpalus commented May 10, 2024

Ah sorry, didn't notice #14186. Closing as duplicate.

@jpalus jpalus closed this May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant