Compiling - Windows

[Rasbats]

Using a relatively clean notebook PC with Win10/Visual Studio 15 2017.

Followed the steps outlined in Compiling - Windows.

Used the pre-built binaries of wxWidgets. Needed to correct the download link for the zip file of these on the manual page.

Needed to install GNU gettext in addition to the other required programs:
http://gnuwin32.sourceforge.net/packages/gettext.htm

I will add this to the manual page.

[Rasbats]

Added. Please delete this issue when the manual is rebuilt.

[rgleason]

I noticed what I think is an error in the rebuild of the manual

Under
https://opencpn-manuals.github.io/main/ocpn-dev-manual/5.3.1/od-compile-windows.html#_getting_and_building_opencpn_source

The git instructions for building debug etc are gone and an * is there.  I think this is a mistake.
Building OpenCPN

    In the open x86 Native Tools Command Prompt for VS 2017 execute the following commands to create the build directory, generate the solutions files and build the debug version, the release version and the setup package.

*

I think we need to add back in the full set of instructions at the asterick.

[rgleason]

Also down at
BatchUtil https://opencpn-manuals.github.io/main/ocpn-dev-manual/5.3.1/od-compile-windows.html#_batchutils
Aren't these outdated commands for building?
I think the batch file should be changed to the proper commands for NOW
Has transmitterDan kept this updated in his git repos?
https://github.com/transmitterdan/BatchUTILS

Yes I believe so, but check with TDan.

#- cmd: nmake -f makefile.vc BUILD=release SHARED=1 CFLAGS=/D_USING_V120_SDK71_ CXXFLAGS=/D_USING_V120_SDK71_
  #- cmd: nmake -f makefile.vc BUILD=debug SHARED=1 CFLAGS=/D_USING_V120_SDK71_ CXXFLAGS=/D_USING_V120_SDK71_

[Rasbats]

I think we need to add back in the full set of instructions at the asterick.

The asterisk needs removing. The commands given do the work.

[Rasbats]

BatchUtil https://opencpn-manuals.github.io/main/ocpn-dev-manual/5.3.1/od-compile-windows.html#_batchutils

"Page not found". Can this issue be closed?