Replies: 3 comments
|
@ravidavi preciso falar com voce.... como consigo contato com voce? |
0 replies
|
I'm late to the party, but we did get them all individually. I don't recall if they were in binary form of in source that we had to compile, but it was the simplest way we found, instead of trying to fit something half working. |
0 replies
|
vcpkg seems to work the best these days: https://github.com/microsoft/vcpkg Install that, run "vcpkg install [library]" for each dependency, and point the OSG 3rdParty entry in cmake to the vcpkg/installed/ directory. It should find each lib and compile with it fine. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi all!
For many years now, I have relied on the prebuilt OSG 3rd-party dependencies from osgVisual. The links are in the old osg website, under Visual Studio 2017. This was very convenient since it had lots of Windows dependencies, plus other useful packages like gdal, nicely packaged and ready to use.
I noticed that the osgVisual website no longer exists, so those prebuilt dependencies are gone. And I wasn't able to find them hosted elsewhere.
So I'm wondering, where do you all go for the osg 3rd party dependencies? Do you get them individually? Compile them via https://github.com/bjornblissing/osg-3rdparty-cmake but get gdal separately? Something else?
Thank you in advance!
All reactions