Two things to try:
The quickest is to simply set the portfile.cmake to an osgearth 2.10 commit here:
REF 342fcadf4c8892ba84841cb5b4162bdc51519e3c #version 3.1
SHA512 03378a918306846d2144e545785c783b01e33fa2dd5c77d16d390a275217b6ce7a3a743c35ae99a497b272a7516b055442c0a891bd312cce727a5538b40364f5
The two need to match to set the REF to a github osgearth commit from 2.10 and either find the SHA or run vcpkg install osgearth and you will get an error message about a found SHA and expecting SHA so paste in the expecting value and try again.
The issue with that is what Glenn mentioned, if you are current on vcpkg, the dependencies such as GEOS or GDAL might be a problem.
The other choice is to roll back to an earlier commit of vcpkg that contained the osgearth 2.10 portfile. That should get you a working osgearth with the dependencies at the time. Problem is you are stuck at that vcpkg commit.
Also keep in mind that vcpkg is just local to the folder so if you want to try either, just make a new folder, git pull vcpkg, and ./bootstrap
.
--
Paul Levy : Pelican Mapping
On Wed, Jan 13, 2021 at 8:16 AM gwaldron [via osgEarth] <
[hidden email]> wrote:
I believe you would have to checkout the old vcpkg portfiles for osgEarth 2.10.
Look here and find the commits from Dec 2018:
https://github.com/microsoft/vcpkg/commits/master/ports/osgearth
Of course, this will cascade into older dependencies as well, so you may need a complete vcpkg checkout from that time period. Good luck.
Glenn Waldron / Pelican Mapping
Locked
