After some effort I have at last succeeded in creating an fgfs executable in Windows, using VS2017 and the instructions located here:
http://wiki.flightgear.org/Building_usi ... _-_Windows
I know I took a risk by using VS2017, when it said it was only tested with VS2015, but I had heard reports that others had done it with 2017 so I went for it.
But in any event, I have a build, and it crashes immediately on startup. It sometimes gets as far as making a flightgear-sized window frame before it crashes, but that's about it.
I have tried looking at the log, which ends on the following warning, but I'm suspicious that this is not my actual problem since there are a lot of previous warnings, and I don't see anything labeled ERROR in there:
20.97 [WARN]:io f:\flightgear\fgmeta\simgear\simgear\scene\model\modelregistry.cxx:657:Image loading failed:
I have tried to run it in debug mode, and I get a bad memory allocation crash off in SimGear at osgDB::RegisterDotOsgWrapperProxy effectGeodeProxy, but it lacks debug information to go any higher than that in the stack trace.
And now, whoops, I just noticed that since I tried upgrading my 2017 build to a later version of the same year (for probably bad reasons) I now can't build any of it, and probably have to go back to CMake.
I guess I will try going back and installing VS2015 and doing the whole thing again. But any advice re: debugging would be very helpful. For instance, is there anything like pdb files that I need to move around in order to get a full stack trace across the FlightGear and SimGear/OSG projects? I'm an long time VS user but have gaps in my knowledge (to say the least) when it comes to the finer points of debugging.
Cheers,
Chris