I would consider twice if upgrading my toolchain is really that impossible. If you still answer yes, consider it once again and then have a look at my (sure incomplete, sure missing trivial code changes that are sometimes needed, in some cases probably actually missing information essential to finally make it build successfully) notes at https://github.com/nohal/OpenCPN/wik...--11-migration
(Fresh from the latest rebuild
with VS2017) and https://github.com/nohal/OpenCPN/wik...-Windows-build
(older, without cairo)
These libraries were not needed for the old OpenCPN
versions built with VS2010, so some of them may not be buildable with it at all in their current
versions, we really don't know (and don't care).
If you do not care about XP compatibility, which anyway probably is not an issue with VS2010 and it's v100 toolchain and which is the main reason we must build all these dependencies ourselves and not use something precompiled found on the Internet
, you may try to find that something somewhere on the Internet
This is one of the most annoying OpenCPN
related operations I have to do with every change of the toolchain, really don't recommend it to anybody.
And yes, it is just a question of time C++11 code will start appearing in OpenCPN's codebase, which will make your toolchain totally unusable.