Errors compiling for first time

[wholybee]

I am attempting to compile OpenCPN for the first time. Fresh install of all the tools following directions here:
https://opencpn.org/wiki/dokuwiki/do...piling_windows

Downloaded and installed versions:
VS Community 2015 12.0.40629.00 Update 5
Git 2.16.2
cmake 3.11.0 rc2
Poedit 2.0.6 (5225)
NSIS (Sourceforge seems to be down indefinitely. Is there another place to d/l this? In any case, I didn't seem to get as far as to need this before I ran into problems)
wxWidgets 3.1.1
Dependencies installed from here: https://sourceforge.net/projects/ope...in.7z/download

Everything went fine until step 4.2a:


"C:\Users\wholybee\Documents\GitHub\OpenCPN\build\ ALL_BUILD.vcxproj" (default t
arget) (1) ->
"C:\Users\wholybee\Documents\GitHub\OpenCPN\build\ WXSVG.vcxproj" (default targe
t) (13) ->
(ClCompile target) ->
C:\Users\wholybee\Documents\GitHub\OpenCPN\src\wxs vg\src\svgxml\svgxml.cpp(24
): fatal error C1083: Cannot open include file: 'expat.h': No such file or dire
ctory [C:\Users\wholybee\Documents\GitHub\OpenCPN\build\W XSVG.vcxproj]

17 Warning(s)
1 Error(s)

Time Elapsed 00:03:20.78

[nohal]

wholybee...
You are using the old dependency bundle, which works only until OpenCPN 4.8.2 (This tag: https://github.com/OpenCPN/OpenCPN/releases/tag/v4.8.2) and a few commit beyond.

The main build instructions for Windows are not yet updated as the master branch still did not settle down completely for the O5 development cycle, but you can find the draft targeting the current codebase at https://github.com/nohal/OpenCPN/wik...n-Windows---O5
And FWIW we never used VS2015, so neither the old one nor the new one will make you happy as they use different MSVC runtimes than the one you have.

And Sourceforge downloads seem to mostly work - https://sourceforge.net/projects/nsis/files/NSIS%203/

Pavel

[wholybee]

Originally Posted by nohal

wholybee...
You are using the old dependency bundle, which works only until OpenCPN 4.8.2 (This tag: https://github.com/OpenCPN/OpenCPN/releases/tag/v4.8.2) and a few commit beyond.

The main build instructions for Windows are not yet updated as the master branch still did not settle down completely for the O5 development cycle, but you can find the draft targeting the current codebase at https://github.com/nohal/OpenCPN/wik...n-Windows---O5
And FWIW we never used VS2015, so neither the old one nor the new one will make you happy as they use different MSVC runtimes than the one you have.

And Sourceforge downloads seem to mostly work - https://sourceforge.net/projects/nsis/files/NSIS%203/

Pavel

Thank you.

VS2015 was a typo, I have VS2013. And I was so careful to do everything exactly right and get the right version numbers in. I will review those links. Sourceforge must be slowly coming up. Earlier today instead of that NSIS page I got a page that said it was in "static mode" and most pages would be unavailable.

[rgleason]

That link didn't seem to work for me but these do.
https://sourceforge.net/projects/opencpnplugins/
https://sourceforge.net/projects/opencpn/

All activity: https://sourceforge.net/p/opencpn/ac...1846326b780f1e

Early version Releases https://sourceforge.net/p/opencpn/news/

opencpnplugins all activity: https://sourceforge.net/p/opencpnplu...8f3d01fa508c0c

[rgleason]

I am finding that the Sourceforge "File Tab" is not working and we are unable to access and download the OpenCPN_buildwin.7z files. See this page for Compiling Windows Are others having troubles? If so, I think we should try to get critical files off sourceforge and hosted locally.

http://sourceforge.net/projects/open...in.7z/download

I get 500 Errors "Oh snap! We can't process this request."

[nohal]

Originally Posted by rgleason

I am finding that the Sourceforge "File Tab" is not working and we are unable to access and download the OpenCPN_buildwin.7z files. See this page for Compiling Windows Are others having troubles? If so, I think we should try to get critical files off sourceforge and hosted locally.

http://sourceforge.net/projects/open...in.7z/download

I get 500 Errors "Oh snap! We can't process this request."

Rick...
Take on the panic harness and simply let them fix it as usually. There really is no need to start a storm of posts every time something has a hiccup. If the problem persists, we will take care of it.

Pavel

[wholybee]

Originally Posted by nohal

wholybee...
You are using the old dependency bundle, which works only until OpenCPN 4.8.2 (This tag: https://github.com/OpenCPN/OpenCPN/releases/tag/v4.8.2) and a few commit beyond.

The main build instructions for Windows are not yet updated as the master branch still did not settle down completely for the O5 development cycle, but you can find the draft targeting the current codebase at https://github.com/nohal/OpenCPN/wik...n-Windows---O5
And FWIW we never used VS2015, so neither the old one nor the new one will make you happy as they use different MSVC runtimes than the one you have.

And Sourceforge downloads seem to mostly work - https://sourceforge.net/projects/nsis/files/NSIS%203/

Pavel

Starting from scratch, following the draft document and using VS2017 and the 4.99 dependency bundle I get the same error. I note that expat.h DOES exist in C:\Users\wholybee\Documents\GitHub\OpenCPN\buildwi n\expat-2.1.0\include. Is there a misconfiguration of an include path somewhere?



"C:\Users\wholybee\Documents\GitHub\OpenCPN\build\ ALL_BUILD.vcxproj" (default t
arget) (1) ->
"C:\Users\wholybee\Documents\GitHub\OpenCPN\build\ WXSVG.vcxproj" (default targe
t) (13) ->
(ClCompile target) ->
C:\Users\wholybee\Documents\GitHub\OpenCPN\src\wxs vg\src\svgxml\svgxml.cpp(24
): fatal error C1083: Cannot open include file: 'expat.h': No such file or dire
ctory [C:\Users\wholybee\Documents\GitHub\OpenCPN\build\W XSVG.vcxproj]

11 Warning(s)
1 Error(s)

Time Elapsed 00:03:58.40

[nohal]

Originally Posted by wholybee

Starting from scratch, following the draft document and using VS2017 and the 4.99 dependency bundle I get the same error. I note that expat.h DOES exist in C:\Users\wholybee\Documents\GitHub\OpenCPN\buildwi n\expat-2.1.0\include. Is there a misconfiguration of an include path somewhere?



"C:\Users\wholybee\Documents\GitHub\OpenCPN\build\ ALL_BUILD.vcxproj" (default t
arget) (1) ->
"C:\Users\wholybee\Documents\GitHub\OpenCPN\build\ WXSVG.vcxproj" (default targe
t) (13) ->
(ClCompile target) ->
C:\Users\wholybee\Documents\GitHub\OpenCPN\src\wxs vg\src\svgxml\svgxml.cpp(24
): fatal error C1083: Cannot open include file: 'expat.h': No such file or dire
ctory [C:\Users\wholybee\Documents\GitHub\OpenCPN\build\W XSVG.vcxproj]

11 Warning(s)
1 Error(s)

Time Elapsed 00:03:58.40

The CI builds on Appveyor do follow those instructions with every single commit and work, so the issue is only specific to your system.
To start with, we now use expat 2.2.5 and it is included in the dependencies bundle, so I wonder how is it possible that you start form scratch, follow the instructions and still end up having the old dependencies containing expat 2.1.0...

[wholybee]

Originally Posted by nohal

The CI builds on Appveyor do follow those instructions with every single commit and work, so the issue is only specific to your system.
To start with, we now use expat 2.2.5 and it is included in the dependencies bundle, so I wonder how is it possible that you start form scratch, follow the instructions and still end up having the old dependencies containing expat 2.1.0...

Hmm.

Well, I started over by restoring a snapshot on the VM before starting. But clearly, you are right. Perhaps it was a lack of sleep and going through it too many times. Both the difficulties with sourceforge, and having gone through it a few times with the old document, and having both the new and old dependencies available locally when I finally got the draft document I must have used the wrong one.

Trying again after a good night sleep.

[rgleason]

It works now Thanks. I don't like the site, sadly.

Originally Posted by nohal

Rick...
Take on the panic harness and simply let them fix it as usually. There really is no need to start a storm of posts every time something has a hiccup. If the problem persists, we will take care of it.
Pavel