Need oCPN binary dependancies for Win 7 / vs2010 / wxLib 3.0.3 / oCPN 4.6.1 build...

[evendine]

For several reasons, upgrading to VS 2013 isn't an option at the moment, so need to build the the binary dependencies for vs2010 as mentioned in the 'Compiling on Windows' section 3.1 of the manual:
https://opencpn.org/wiki/dokuwiki/do...piling_windows

Have checked the available pre-compiled binary collections on Sourceforge (see: https://sourceforge.net/projects/opencpnplugins/files/opencpn_packaging_data/), but according to Dependency Walker, the runtime libraries for the files are vc120, rather than the vc100 needed.

Does anyone have the codebase / solution / CMake files needed to generate the following dll's?

• libcurl.dll
• cairo.dll
• fontconfig.dll
• pixman-1.dll
• libpng.dll
• zlib.dll
• expat.dll

Have looked in the prior version repositories on Github (e.g. https://github.com/OpenCPN/OpenCPN/tree/v4.6.1/src) but can't find the collection of files needed to build the binary dependencies. Any suggestions / advice much appreciated...

[nohal]

evendine...

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.

Pavel

[evendine]

Hi Pavel,

thanks for the info - completely with you on the problems involved in toolchain / codebase maintenance in complex solutions. It may seem old fashioned, but it's one reason i tend to use static builds - 'dll hell' is no fun, that's for sure!

Trying to avoid having to maintain multiple development system versions, but as you say, c++ 11 support is becoming essential.

Wonder if the 'Native Retargeting' features of VS2017 (just came across this today) might provide a solution / be of help?

https://blogs.msdn.microsoft.com/vcb...-your-toolset/

All the best,

Martin

[nohal]

Originally Posted by evendine

Hi Pavel,

thanks for the info - completely with you on the problems involved in toolchain / codebase maintenance in complex solutions. It may seem old fashioned, but it's one reason i tend to use static builds - 'dll hell' is no fun, that's for sure!

Trying to avoid having to maintain multiple development system versions, but as you say, c++ 11 support is becoming essential.

Wonder if the 'Native Retargeting' features of VS2017 (just came across this today) might provide a solution / be of help?

https://blogs.msdn.microsoft.com/vcb...-your-toolset/

All the best,

Martin

Martin...
I of course have no idea what are those "several reasons" that make you want to compile OpenCPN with VS 2010. There is no problem having various versions of VisualStudio on the same machine as far as I can tell.

The link you provided talks about exactly this (Which also is what we use to maintain the XP backward compatibility), just taken to the extreme with many platform SDKs and compiler toolsets installed at the same time.

Said all this optimistic crap:
I personally use dedicated VMs, installed from scratch with only one VS version on them to be sure I know what's going on with my builds.
As far as I can tell, it is just Microsoft's wet dream that this stuff is not problematic at all. But you don't know until you try...

Pavel

[evendine]

Hi Pavel,

as mentioned earlier, would rather not have several MS development environments, as am developing cross platform in any case, so have enough already!

oCPN is only part of the problem - i have a large, complex realtime development to maintain, which has caused problems when migrated between MS environments in the past. Right now, stability is the priority for a range of reasons, although the system will need c++ 11 in future, so migration will happen at some point.

I may just install vs2017 on another machine for now, as (hopefully - it's MS) it will solve the issues with the oCPN build...

[rgleason]

Originally Posted by evendine

For several reasons, upgrading to VS 2013 isn't an option at the moment, so need to build the the binary dependencies for vs2010 as mentioned in the 'Compiling on Windows' section 3.1 of the manual:
https://opencpn.org/wiki/dokuwiki/do...piling_windows

Have checked the available pre-compiled binary collections on Sourceforge (see: https://sourceforge.net/projects/opencpnplugins/files/opencpn_packaging_data/), but according to Dependency Walker, the runtime libraries for the files are vc120, rather than the vc100 needed.

Does anyone have the codebase / solution / CMake files needed to generate the following dll's?

• libcurl.dll
• cairo.dll
• fontconfig.dll
• pixman-1.dll
• libpng.dll
• zlib.dll
• expat.dll

Have looked in the prior version repositories on Github (e.g. https://github.com/OpenCPN/OpenCPN/tree/v4.6.1/src) but can't find the collection of files needed to build the binary dependencies. Any suggestions / advice much appreciated...

Sent an email to you with a link about 15mb. I have no idea whatsoever if it is complete. No promises. Please let me know if it works and what changes were necessary. I might package it and keep it for awhile.