OpenCPN Build on Win32

[bdbcat]

Gunther....

OK, lets get some new tools.

1. InspectEXE

Inspect Exe

download and install the free version of InspectEXE.

2. Right click->Properties->InspectEXE->TestLoad

Do this for the locally built wxWidgets dlls, and also for the git package dlls.
Compare the results.

We are interested in the entry regarding MSVCR??.dll.

I think the local dlls will load OK, but the package dlls will fail to load. Please confirm.

Thanks
Dave

[Netsurfer]

Dave,

Originally Posted by bdbcat

Gunther....

OK, lets get some new tools.

1. InspectEXE

Inspect Exe

download and install the free version of InspectEXE.

2. Right click->Properties->InspectEXE->TestLoad

OK - done.

Do this for the locally built wxWidgets dlls, and also for the git package dlls.
Compare the results.

We are interested in the entry regarding MSVCR??.dll.

I think the local dlls will load OK, but the package dlls will fail to load. Please confirm.

I try to do my best - not quite sure what is the point of the matter ... .

I added two screenshots (as copy isn't available from the freeware version). The first one shows the result of Test Load for a DLL file from GIT, whereas the second one is from the locally build DLL.

Let me know if you need further information (and how do I get them).

Maybe one reason for problems may be that I have also installed MS Visual Studio 2010 on my system? And I still haven't solved the issue with the localization thing (using decimal point) - do you remember?
So maybe it is again an individual problem ... .

Thanks,

Gunther

[bdbcat]

Gunther, and others....

Here is what I have done:

1. Convert MSW build process to VS2008, using VC90 toolset.
2. Add VC90 redistributable package to the installer.
3. Compiled wxWidgets dlls using VC90.
4. Removed time_t size definition from wxWidgets and opencpn.
5. Pushed to git

What this all means to users doing local compilation of opencpn on VS2008 is this: If you are going to use the PACKAGE target, then the local building of wxWidgets for release mode is not necessary. The PACKAGE project in the VS solution will use the embedded wxWidgets dlls to build the binary installer.

Of course, if you want to debug opencpn in VS2008, you will need to build debug wxWidgets dlls, and manually move them to the right place in the opencpn build directory tree.

This also should work with VS2010, although I have not yet tested it. VS2010 allows the specification of VS90 toolset in lieu of VC100, its default.

I tested the resulting installer binary on a virgin Win7 (virtual), and all was well.

I am still looking for a volunteer to take over building and uploading the Windows installer binary at each Beta release. It should be cookbook clear with these latest changes.

Good Luck
Dave

[Netsurfer]

Dave,

at first the good news - I was still able to build the opencpn.exe and the package.

Originally Posted by bdbcat

What this all means to users doing local compilation of opencpn on VS2008 is this: If you are going to use the PACKAGE target, then the local building of wxWidgets for release mode is not necessary. The PACKAGE project in the VS solution will use the embedded wxWidgets dlls to build the binary installer.

Of course, if you want to debug opencpn in VS2008, you will need to build debug wxWidgets dlls, and manually move them to the right place in the opencpn build directory tree.

I have a question concerning the wxWidgets lib/vc_dll:
I use CMake 2.8.2 (cmake-gui). And there is still the local path to the wxWidgets library. Cause you have removed the time_t size definition from wxWidgets and opencpn I first had to compile it without patching (see Pavels tutorial) it afterwards.

This also should work with VS2010, although I have not yet tested it. VS2010 allows the specification of VS90 toolset in lieu of VC100, its default.

I have choosen "Visual Studio 10" and "Use default native compilers" in cmake-gui and changed the toolset for each project from V100 to V90. It worked using VC++2010 EE.

I tested the resulting installer binary on a virgin Win7 (virtual), and all was well.

Thanks for adding the build number to the file name!
Now I got "opencpn_22_730_setup.exe".
Installation worked without any problems on Win 7U 32Bit. No more problems with the 5 DLL files.

But the help files/ doc dir are/ is completely missing.

Other differences I recognized:
Now there also is a NSIS project file ("project.nsi")

I am still looking for a volunteer to take over building and uploading the Windows installer binary at each Beta release. It should be cookbook clear with these latest changes.

As I am doing this for the German site, I could do this also for OpenCPN.org (just need a FTP account to upload the file).

Thanks,

Gunther

[bdbcat]

Gunther....

I'm glad it is working OK for you now.

Where do you find "project.nsi"?

Help files: I removed them from the Windows build to reduce the size of my uploads for Beta testing. I will add them back to CMakeLists.txt.

I will try to set up the ftp account for opencpn.org for you. I may need Will's help.

When we have the account set up, you can do the installer build and upload anytime the git files change so that Windows testers may try the newest bleeding edge code. I will make a more formal announcement on the thread for "official" Beta releases, generally weekly or so as significant bug fixes and/or features are implemented.

Thanks for volunteering, Gunther. I know everyone will appreciate having the Windows installer available on a timely basis.

Dave

[Netsurfer]

Dave,

Originally Posted by bdbcat

Where do you find "project.nsi"?

In my build dir there are (amongst others):
..\Test-Build\_CPack_Packages\win32\NSIS
This directory contains 1 subdir and 3 files:

1. opencpn_22_730_setup
2. NSIS.InstallOptions.ini
3. opencpn_22_730_setup.exe
4. project.nsi

Help files: I removed them from the Windows build to reduce the size of my uploads for Beta testing. I will add them back to CMakeLists.txt.

Ah, OK. If it is intended then it is OK.

I will try to set up the ftp account for opencpn.org for you. I may need Will's help.

When we have the account set up, you can do the installer build and upload anytime the git files change so that Windows testers may try the newest bleeding edge code. I will make a more formal announcement on the thread for "official" Beta releases, generally weekly or so as significant bug fixes and/or features are implemented.

I'll do.
And how about the build numbers (versions) in the tracker? They are restrained to the "official" Beta releases, aren't they?

Gunther

[Netsurfer]

Dave,

actually there seems to be at least one problem creating the mo files.
Though I get the following message for all languages

"D:\Program Files\gettext-tools\bin\msgmerge.exe" --width=80 --strict --quiet --update --backup=none --no-location -s F:/GIT/opencpn/po/opencpn_de_DE.po F:/GIT/opencpn/po/opencpn.pot

the po files are not created at all.

Therefor the build process for the installer fails as it complains (for each language):

2>CMake Error at F:/Build_01/cmake_install.cmake:91 (FILE):
2> file INSTALL cannot find "F:/Build_01/opencpn_cs_CZ.mo".

Or did I make a mistake?

Thanks,

Gunther

Addition 1:
Built the mo files manually and copied to the build dir.
Files are erased by the build process.

11>CMake Error at F:/Build_01/cmake_install.cmake:91 (FILE):
11> file INSTALL cannot find "F:/Build_01/opencpn_cs_CZ.mo".

[Ptizef]

Hi , All

I succeeded to migrate to GIT and got new sources . Many thanks to Gunther,Pavel,viking sailor ...
Now I have to compile and that's another story !

Until now I used to built with vc++ 2008 , but now ,if it's still works for the main part, plugins are not built
I tried to use cmake gui but I got the errors messages in the shot attached
I don't know what to do with wxWindgets . I read .org's wiki but didn't understand well .
If somebody can help me ?
Many thanks
Jean Pierre

[nohal]

JP,
the building instructions on the wiki are already outdated as Dave made some changes to the configuration process, so patching WX projects is not necessary anymore. I will update the instructions shortly.
In short:
Download wxMSW and install it
Open wx_dll.dsw (should be in C:\wxWidgets-2.8.10\build\msw if you install in default location) and convert all the projects to VS2008 format (it will ask you, just answer Yes to everything)
Choose "DLL Debug" from the list of build targets and compile wxWidgets
Choose "DLL Release" from the list of build targets and compile wxWidgets
This way you will have all the necessary DLLs

Now you should be able to run cmake to generate the solution for OpenCPN

Pavel

[Netsurfer]

Jean Pierre,

Originally Posted by Ptizef

Until now I used to built with vc++ 2008 , but now ,if it's still works for the main part, plugins are not built
I tried to use cmake gui but I got the errors messages in the shot attached
I don't know what to do with wxWidgets . I read .org's wiki but didn't understand well .

you have to download and install wxWidgets.
See: Downloads - wxWidgets
I used Download wxWidgets from SourceForge.net

Extract the archive to your harddisk.
Now follow the steps described at Compiling the Source in Windows | Official OpenCPN Homepage
under
Pre-requisities
WxWidgets
Convert the solution to VC++ 2008 format

Do this once for 'Release' and once for 'Debug'.

Also important is to add the path to your local '<drive>:\<path to ...>\wxWidgets-2.8.11\lib\vc_dll' directory to the Windows PATH variable!
You need to reboot your system to take effect of these changes!

The GTK2 complains of cmake-gui can be ignored as it is not necessary.

Nohal was quicker than me ..., so I stop here.
If you have further questions, just ask.

Gunther

[nohal]

Originally Posted by Netsurfer

Built the mo files manually and copied to the build dir.
Files are erased by the build process.

Gunther,
just get http://ftp.gnome.org/pub/gnome/binar...ime-0.17-1.zip and unpack it to the same folder as gettext - for whatever reason intl.dll is missing from gettext-tools package.

I updated the building instructions in the wiki so they reflect the latest state and should be a bit more bulletproof. Let me know if they seem clear or need more refinement.

Pavel

[Netsurfer]

Pavel (, Dave)

Originally Posted by nohal

... for whatever reason intl.dll is missing from gettext-tools package.

thanks for the information!

Just pushed the intl.dll from the download to my existing bin dir and everything works perfectly again!

Could build everything without any problems.

Thanks,
Gunther

[Ptizef]

Gunther, pavel
Many thanks for your help
I've done all what you told me . (at least I hope so ..)
Cmake gui return two errors
-The GTK complaint you told me must be ignored OK
-wxwidgets_wxrc_EXECUTABLE_NOTFOUND
when I click once more on "configure" , I get "generate" and the project is generated . May be it's not important ?

The (new) problem is when compiling in vc++, with this generated opencpn.vcproj , I get errors (see shot attached)
Do I have missed something ?
thanks
Jean Pierre

[nohal]

Originally Posted by Ptizef

Gunther, pavel
Many thanks for your help
I've done all what you told me . (at least I hope so ..)
Cmake gui return two errors
-The GTK complaint you told me must be ignored OK
-wxwidgets_wxrc_EXECUTABLE_NOTFOUND
when I click once more on "configure" , I get "generate" and the project is generated . May be it's not important ?

You are there, both of these can be ignored.

The (new) problem is when compiling in vc++, with this generated opencpn.vcproj , I get errors (see shot attached)
Do I have missed something ?

That's the time_t problem which was solved by the latest modifications Dave made to the configuration process. To deal with it in your environment, do the following:

• In wxWidgets build/msw folder delete *.vcproj and *.sln, open ws_dll.dsw in Visual Studio and do the conversion to VS2008 format
• Do the full rebuild (Ctrl+Alt+F7) of DLL Debug and DLL Release targets (it's important not to do just a normal build but to really recompile everything)
• Delete the contents of OpenCPN build directory
• Make sure you have the latest git source for OpenCPN - go to the source directory and do

  git pull origin

• Do the cmake stuff to generate the solution and projects
• Open OpenCPN.sln
• Do the build

OpenCPN should build cleanly.

Pavel

[Netsurfer]

Originally Posted by Netsurfer

Could build everything without any problems.

Still a problem with OCPN.
Switching the locale setting has no effect, or to be more precise:
The setting is written to opencpn.ini. But regardless of the setting/ entry it is always the English mo file used.

In the dir tree in every 'LC_MESSAGES' dir there is one file called 'opencpn.mo' and differ in size in each of the locale dirs.

Is it a bug in the OCPN core?

Gunther