Beta Test / Technical

[rgleason]

Win10, using TDan Batchutil setup to compile the most recent Opencpn (master).
I have run 'build clean' and 'build' which includes all the usual cmake commands
and get one error:

Build FAILED.
"C:\Users\..\GitHub\OpenCPN\build\ALL_BUILD.vcxpro j" (default target) (1) ->
"C:\Users\..\GitHub\OpenCPN\build\WXSVG.vcxpro j" (default target) (13) ->
(ClCompile target) ->
C:\Users\..\GitHub\OpenCPN\src\wxsvg\src\svgxml\ svgxml.cpp (24) : fatal error C1083: Cannot open include file: 'expat.h': No such file or directory [C:\Users\..\GitHub\OpenCPN\build\WXSVG.vcxproj]
1 Error(s)

Is this a dependency error? It was compiling before. Still using MSVC++2013 and wxWidgets 3.0.2

I find expat.h under C:\Users\Frederick\Documents\GitHub\OpenCPN\buildw in\expat-2.1.0\include

C:\Users\Frederick\Documents\GitHub\OpenCPN\src\wx svg\src\svgxml\svgxml.cpp
Line 24
#include "svgxml.h"
#include <expat.h>

Is this a path problem?

[transmitterdan]

Delete CMakeCache.text and run Cmake again. Also, make sure you have a recent version of Cmake.

[nohal]

Originally Posted by transmitterdan

Delete CMakeCache.text and run Cmake again. Also, make sure you have a recent version of Cmake.

That is very unlikely to resolve anything. The missing file is part of the new dependency bundle being prepared for O5.
But it makes very little sense to do these builds the way Rick was used to do in the past as you can simply download them from https://ci.appveyor.com/project/bdbc...uild/artifacts

Pavel

[transmitterdan]

I successfully built O from git master last night. I will stand by awaiting the new dependencies.

Can we debug in MSVC with the appveyor built images? I thought to debug one has to build locally from sources?

[nohal]

Originally Posted by transmitterdan

Can we debug in MSVC with the appveyor built images? I thought to debug one has to build locally from sources?

Not at the moment, but we may start publishing also the PDBs when the situation settles down a bit.
Of course if you do a local debug build, your possibilities are much better than from a release build, even with the debugging symbols available.

[rgleason]

I guess as Pavel says, with Appveyor builds working, it makes little sense to build yourself (unless you are debugging).

However I deleted cmakeCache.txt and ran cmake -T v120_xp .. and cmake --build . --config release

and got the same error as Pavel said I would.

So why does it run in CI under appveyor and not for my manual operation. It will be a very long time before I understand this. If I were to put a second copy of expat.h in the subdirectory, would it compile?

I am not wanting to let go of the ability to compile.

[transmitterdan]

Cl is using VS2017. Once the dependencies are all set up we will be using VS2017 going forward. It's unlikely VS2013 will work once everything is set up. Pavel has instructions on github for building with VS2017.

[rgleason]

TDan Do you think I should stay with VS2013 and wx 3.0.2 until we know all PI are compiled and updated for 4.8.2?

Or should I just move on?
Being in the middle of these changeovers is always interesting.
Maybe I leave one machine for 4.8.2 and move on with the other.

[nohal]

Originally Posted by rgleason

TDan Do you think I should stay with VS2013 and wx 3.0.2 until we know all PI are compiled and updated for 4.8.2?

Or should I just move on?

Rick...
We need to do tons of plugin releases for O4.8.2, with the VS2013 toolchain. And we certainly want help with that. What we do not need help with at this moment is duplicating the CI builds with the new toolchain. I know it is boring to play with older toys, but that is what we really need...

Pavel

[kevinvh]

Originally Posted by nohal

Rick...
We need to do tons of plugin releases for O4.8.2, with the VS2013 toolchain. And we certainly want help with that. What we do not need help with at this moment is duplicating the CI builds with the new toolchain. I know it is boring to play with older toys, but that is what we really need...

Pavel

We love to get our hands on new toys. An unwanted and unnecessary distraction for you Pavel - I completely understand. So we should all standby and wait for the next major instalment unless we have constructive changes to suggest - I agree with that also!

[Baikal]

For O5, WxW has been updated to see if the problem described here will be fixed
http://www.cruisersforum.com/forums/...ml#post2569805
http://www.cruisersforum.com/forums/...ml#post2569815

[cagney]

There is a small problem in todays git (4.99)
I get this error when installing

CMake Error at cmake_install.cmake:126 (file):
file INSTALL cannot find
"/home/thomas/Sailing/OpenCPN/OpenCPN/data/opencpn-64.png".

The opencpn-64.png file is there in the code but it's not moved to the correct directory for installation.

Thomas

[nohal]

Originally Posted by cagney

There is a small problem in todays git (4.99)
I get this error when installing


The opencpn-64.png file is there in the code but it's not moved to the correct directory for installation.

Thomas

Fixed.

Pavel

[rgleason]

Pavel / Dave,

I'd like to git checkout v4.8.2 but do not find that in the opencpn branches. I am too far into v4.99 to compile with MSVC++2013.
Can you give me the release 4.8.0 code or add a tag please?

Thanks

I found this under Commits "Release 4.8.2"

https://github.com/OpenCPN/OpenCPN/c...6728be71216ab3

and it shows a Master v4.8.2 Tag but that branch is not showing in my local repository, the link leads to

https://github.com/OpenCPN/OpenCPN/releases/tag/v4.8.2 and the code is

• bcbda2a

So I"ll try that.
It worked, but we lost the tag v4.8.2 probably because the permissions were fixed?
Would be nice to have something in the beginning of the title with "v4.8.2" if possible.
Maybe the title could be edited?

Well, using the "hash" code ends me up in detached head state. I guess I must use the long tag to avoid that.

[rgleason]

Forgot I need to make a local branch too..

git checkout -b v4.8.2 -bcbda2a

should do it. would be nice to have the tag.

C:\Users\...\OpenCPN>git checkout -b v4.8.2 bcdba2a
fatal: Cannot update paths and switch to branch 'v4.8.2' at the same time.
Did you intend to checkout 'bcdba2a' which can not be resolved as commit?

This worked. I guess the Tag is seen by git, but not by us. I am talking about the remote tag v4.8.2 seems to get covered by the title "Fix the permissions..."

C:\Users\...\GitHub\OpenCPN>git checkout -b v4.8.2
Switched to a new branch 'v4.8.2'

checked

C:\Users\...\GitHub\OpenCPN>git branch -va
master ca6286e Merge pull request #1005 from seandepagnier/llregion_optimization
* v4.8.2 bcbda2a Fix the permissions on documentation files