VS2017 Compilation Issues (C1083)

[FightOrFlight]

I am trying to compile the Superbuild on Windows 7 and encountered a couple of errors I cannot resolve.


I am not sure if I am missing something or not, or how to resolve it telling me those files cannot be opened.

[wkitty42]

it is saying that they don't exist... non-existent files cannot be opened

[FightOrFlight]

Except the files appear in my explorer, so I'm not sure what to do to make VS recognize them

[legoboyvdlp]

Looks like curl itself is not installed, same for the other libraries. It's finding the OSG plugins ok but they reference the other libraries including curl. Did you point cmake to curl with CURL_INCLUDE_DIR etc?

[FightOrFlight]

I just made it point to where curl.exe is located but it doesn't seem to have changed anything. I also added it to PATH.

[legoboyvdlp]

There'll be other commands to run too - libraries usually have a include directory and a lib directory

If you run CMAKE it shouldn't generate a build solution if it can't find what it needs so I'm not sure how you got as far as Visual Studio

[FightOrFlight]

I tried adding the missing libraries to CMake GUI as I discovered them, but the generated project doesn't seem to care. It gives me an OPENAL_LIBRARY warning despite having it defined in CMake GUI.

[chriscalef]

Hi, just wondering if this issue ever got resolved, or if anyone is currently building FG with VS 2017. I'm in the same boat at the moment.

And, while I'm at it... is there any way that FG could be linked to a finished OSG binary/lib/DLL? I have good reasons for wanting to build my own flightgear exe in Windows, but I have zero interest in doing any work related to OSG, and it seems to be a real sticky spot in the build pipeline given all the many and diverse dependencies.

All advice welcome!

[chriscalef]

Okay, I haven't tried this yet, but before I forget to post it here, I got some advice on the mailing list from Brendan Black, which should be of use to anybody else stumbling down this path:

-----------------------------

The method I usually follow is here:

http://wiki.flightgear.org/Building_usi ... _-_Windows

The method gets you to grab build artifacts for 3rd part libraries & OpenSceneGraph

I have verified it with Visual Studio 2017 on Windows 10 (it doesn't work with 2019 for me), for which you don't need to install any Windows 7 SDK - the VS2017 installer installs a Win10 SDK which seems to work ok. I have to say I only build 64 bit, so I can only very that a 64 bit build works.