[osgearth] Fix undefined references due to openjp2 and xml2#17993
[osgearth] Fix undefined references due to openjp2 and xml2#17993strega-nil-ms merged 3 commits intomicrosoft:masterfrom
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Thanks for fixing this problem. Can you run |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@NancyLi1013 , Thanks for updating the PR . Looks all green now. |
|
I try to build After added xml2 to the fix-dependency-osg.patch, then rebuild, the errors which are related with Seems it also needs to link |
|
Can you post the error you encountered on your machine before you fix the dependent patch? @ankurverma85 |
|
@NancyLi1013 This is also from gdal. |
|
pasting the errors I'm seeing |
|
Thanks for your details. But I still have one question here. I didn't encounter |
Did you build for x64-linux (static linkage)? |
|
Thanks for your quick reply @dg0yt.
I build the default triplet, so it should be static linkage.
I actually have installed
I didn't do any changes for |
#9068 and most of my PRs...
It is, normally. Still, gdal must export its usage requirements. |
|
@NancyLi1013 Regarding gdal issues in general: I think we can all agree this PR isn't the long term correct fix. What @dg0yt is highlighting is completely valid and perhaps his PR is the right direction in terms of a long term fix. |
|
Thanks for your details and conclusion @ankurverma85. As talked above, there are many problems in @dg0yt thanks for your help and looking into this. |
|
@NancyLi1013 . This has been lying without merge for a week now |
|
Cool, thanks y'all :) |
Add additional dependencies (for GDAL) openjp2 and xml2 in the explicit linking list
What does your PR fix?
Fixes [osgearth] build failure with x64-linux unresolved references #17992 17992
Which triplets are supported/not supported? Have you updated the CI baseline?
Yes
Does your PR follow the maintainer guide?
Yes
If you have added/updated a port: Have you run
./vcpkg x-add-version --alland committed the result?Yes
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/