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

[vcpkg baseline][poppler] Fix issue with using libcurl. #15491

Merged
merged 3 commits into from Jan 8, 2021

Conversation

Hoikas
Copy link
Contributor

@Hoikas Hoikas commented Jan 7, 2021

This fixes an issue where poppler will attempt to build with libcurl. Libcurl's cmake config file does not properly set its CMake policies so certain if() calls fail, causing a cascade failure in the poppler. Should fix issue seen in #15200.

  • What does your PR fix?
    See above

  • Which triplets are supported/not supported? Have you updated the CI baseline?
    No change

  • Does your PR follow the maintainer guide?
    Yes

@JackBoosY JackBoosY self-assigned this Jan 7, 2021
@JackBoosY
Copy link
Contributor

Can we completely solve this issue instead of simply disabling curl?

@JackBoosY JackBoosY added category:port-bug The issue is with a library, which is something the port should already support requires:author-response labels Jan 7, 2021
@Hoikas
Copy link
Contributor Author

Hoikas commented Jan 7, 2021

Sure. This just seemed like the quickest fix because poppler does not list curl as a dependency.

Otherwise, ports using old (eg pre-2.8) CMake minimums might fail when
they import the package.
@JackBoosY JackBoosY added info:reviewed Pull Request changes follow basic guidelines and removed requires:author-response labels Jan 8, 2021
@JackBoosY JackBoosY changed the title [poppler] Fix issue with using libcurl. [vcpkg baseline][poppler] Fix issue with using libcurl. Jan 8, 2021
@JackBoosY
Copy link
Contributor

Ping @vicroms for merge this PR.

@ras0219-msft
Copy link
Contributor

Thanks for the fix!

@Hoikas Hoikas deleted the fix-poppler-baseline branch January 8, 2021 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support info:reviewed Pull Request changes follow basic guidelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants