Beta Test / Technical

[rgleason]

Deleted the OpenCPN local repository and cloned my OpenCPN repository as "origin", then from cd C:\Compile\Github\OpenCPN\ did

git remote add upstream git://github.com/OpenCPN/OpenCPN.git
git fetch upstream
git checkout -b upstream/master-local
unpack Opencpn-buildwin-4.99.7z to C:\Compile\Github\OpenCPN\buildwin\
mkdir build
cd build
cmake "Visual Studio 15 2017" -Tv141_xp ..
cmake --build . --config release  - WORKED
cpack           -WORKED
 cmake --build . --config debug   - SAME 30 FAILURES

Also tried "cmake --build ." as in the manual.

What am I missing to compile for Debug?

[nohal]

Originally Posted by rgleason

Rebooted the VM and restarted VirtualBox. Changed to MUI branch and tried to compile for debug. Same 30 errors.
Should I just delete and git clone again?

Rick...
As the linker errors you see have nothing to do with the OpenCPN code, deleting and clonning it again will pretty sure not help you with anything.
What probably will help you is fixing your wxWidgets libraries. That will likely be achieved by following the instructions exactly.

Pavel

[rgleason]

I have not copied any of the other files as is done for compiling Opencpn v4.8.8


PS: Thanks Pavel. I just downloaded then from sourceforge and expanded them. Will do it again.
I checked the paths again and they were fine and I had added c:\compile\github\

[rgleason]

I used navnux link and downloaded wxWidgets-3.1.1.7z
and expanded it into c:/wxWidgets-3.1.1 overwriting the earlier version.
Then tried to debug compile and got the same 30 errors.


Is it required that I "Build from source" to successfully compile debug?
Got the answer here:

"Fast way to get started but not suitable for serious development as only release configuration libraries are included."

[rgleason]

Under Release Tag 3.1.1 "For Developers"

For developing applications with wxWidgets you need to download the compiler-independent wxWidgets-3.1.1_Headers.7z file and one of wxMSW-3.1.1-vcXXX_Dev.7z or wxMSW-3.1.1_gccXXX_Dev.7z files depending on your compiler, its version and the target architecture (x86 if not specified or x64).

For Microsoft Visual Basic 2017 do I need "wxWidgets-3.1.1_Headers.7z" and "wxMSW-3.1.1-vcXXX_Dev.7z"?

I found and downloaded both

• wxWidgets-3.1.1_Headers.7z
• wxMSW-3.1.1-vc141_Dev.7z (30mb)

I suppose I extract them to a new github folder wxWidgets-3.1.1 and try to compile them.

So now I've extracted them to "C:\Compile\Github\wxWidgets-3.1.1" but I still have "C:\wxWidgets-3.1.1" and have set paths to that and a system variable. Aren't things going to get confused? Should I move these new files out of Github to "C:\wxWidgets-3.1.1" before compiling?


Have changed it to c:/compille/github/wxWidgets-3.1.1-dev and found this page
OpenCPN Dev Manual "Building from Source"
and Widgets Documentation "Using Cmake"

[rgleason]

Under my download wxWidgets-3.1.1-dev I don't find a build/msw directory, as indicated in the Opencpn compile instructions, but I do find this directory in the github wxWidgets repository https://github.com/wxWidgets/wxWidge...ster/build/msw .

Perhaps I should be simply cloning all of https://github.com/wxWidgets/wxWidgets ?

Should I clone it to a location under my github directory or should it be under C:\wxWidgets-3.1.1?

Also I need to know if I am building a bunch of wxWidgets files that are then copied to C:\wxWidgets-3.1.1 to be used when compiling Opencpn, or if the compiler is going to need the path to wxWidgets in order to compile the needed wxWidgets files when compiling Opencpn (I think not).

[seandepagnier]

Originally Posted by bdbcat

steavad...

I don't believe that the newer syntax will produce measurably faster code, anyway.



So there is no real effort (by me) to convert older working code in OCPN to modern c++ syntax. Let it be, and move ahead with features and bug fixes.

I agree.

I like first-class functions with lambda, map, apply, lexical scoping and even continuations, just not in c++. The new syntax may support the y combinator in c++, but it is so horrible to look at, it's better to use a functional language for this. Furthermore, c++ has so many odd features there are few people who know all of them, and in low level language that can poke memory directly, the potential for difficult bugs seems high.

Maybe we should seriously consider porting bits of opencpn into separate libraries, call from other languages, and still have the efficiency for the cpu intensive tasks like chart parsing, graphics etc.. while making development cycle faster and using much more modern user interfaces and the ability to integrate with other programs. Be able to be used in scripts that pull things from charts, or perform weather routing, or generate blended weather maps with charts or even scripts to create video from radar overlay. These type of scripts would only be few dozen lines at most. This would also make it possible to support opencpn rendering on a tile map server, and many other possibilities.

[rgleason]

I tried using issuing the Ocpn Dev Manual "nmake..." commands from a created build/msw folder resulting in an error. Then tried the cmake gui as suggested in the wxWidgets manual and the source directory "wxWidgets-3.1.1-dev" does " does not appear to contain CMakeLists.txt." A search of this folder shows that cmakelists.txt does not exist at all.


Another dead end.
Screw it.

[rgleason]

Found this from the previous instructions Compile from the command line

Run the Developer Command Prompt for VS2013. Go to your wxWidgets build tree (cd C:\wxWidgets-3.0.2\build\msw) and build both release and debug configurations, compatible with Windows XP

Also there is a note about "This assumes that you have Microsoft SDK 7.1A installed on your pc." for XP support. ---Is this still necessary?


This older documentation seems to be clearer about what to do, IMHO

[rgleason]

nmake is compiling now. I downloaded from here for windows and extracted to c:/wxwidgets-3.1.1 as suggested. Windows can download "Latest Devlopment Release 3.1.1"

[rgleason]

Well nmake may compile wxWidgets with that source, but OpenCPN debug build still has linker errors, so that the link I gave probably does not have all the files needed.
I'll figure this out in the morning.

[transmitterdan]

Originally Posted by rgleason

Well nmake may compile wxWidgets with that source, but OpenCPN debug build still has linker errors, so that the link I gave probably does not have all the files needed.
I'll figure this out in the morning.

Rick,

I have no issues compiling wxWidgets with either VS2013 or VS2017. It links perfectly with O in release or debug.

Maybe it would be more productive to start a PM conversation. I suspect these “stream of consciousness” postings don’t help anyone.

[rgleason]

Sorry, its just static. So pleased you have no problem.

[transmitterdan]

Rick,

I’m willing to help you. Just send a PM.

[rgleason]

Thanks TDan, it's sorted out now.