Climatology

[rgleason]

Just found new changes in git for Climatology_pi. During Cmake --build . --config release found this warning.

..\src\ClimatologyConfigDialog.cpp(247): warning C4800: 'long' : forcing value
 to bool 'true' or 'false' (performance warning) [C:\o-plugin\climatology_pi\bui
ld\climatology_pi.vcxproj]

    1 Warning(s)
    0 Error(s)

[rgleason]

Climatology_pi has been updated as of June 5 EST 8pm

climatology_pi-0.8-win32.exe is located in the
C:\o-plugin\climatology_pi\build\_CPack_Packages\win32\ NSIS
folder.

This file contains the dll, the data subdirectory and a few files. It does not contain all the data files. Those will have to be loaded separately.
See the CL-DATA 10 7z file and uncompress and put in the data directory. please.

Find these files under File Thingie 2.5.7
rguser, rgpass under the 3.3.1731 folder.

[rgleason]

Since this is the Thread where I was trying to make packages I am going to post the solution that works for me.

To make Plugin Packages in Windows
=========

Developers documentation - Compiling Windows
Compiling - Windows | Official OpenCPN Homepage
Compiling - Windows | Official OpenCPN Homepage
Developers Manual, Compiling, Compiling Windows.

On this page go down to NSIS (Unicode) used to build the installation packages for OpenCPN and Plugins

Get it from Downloads - unsis - NSIS branch that supports Unicode. - Google Project Hosting
The NSIS Unicode 2.46 setup file is also included in the GIT repository -> ..\buildwin\NSIS_Unicode\nsis-2.46-Unicode-setup.exe
Direct download link: https://code.google.com/p/unsis/downloads/detail?name=nsis-2.46.3-Unicode-setup.exe&can=2&q=

Download and install it. Due to a "bug" in CMake, which only looks at "HKEY_LOCAL_MACHINE\SOFTWARE\NSIS" for the installation location of NSIS and the Unicode version adds its registry key in "HKEY_LOCAL_MACHINE\SOFTWARE\NSIS\Unicode", there is some registry tweaking needed.

Previously I had not installed this, so I had to do it and I also ran the Batch file mentioned in the Dev Docs that they say to run to make the registry tweaks.
So run that batch file.

Then add under Control Panel > System > Advanced System Settings > Environment Variables > System Variable > Variable = Path under Values add the the path to your NSIS programs EG: "C:\Program Files (x86)\NSIS\Unicode with a colon in front. Be careful with your editing here.

Then reboot.


======
Commands to make an Install Package

In the Command prompt
cd ..\o-plugin\climatology_pi\build
cmake ..
cmake --build .
cmake --build . --config release
cpart <-- this does the package! just "cpart"

If successful, you will find your packaged exe in this file
C:\o-plugin\climatology_pi\build\_CPack_Packages\win32\ NSIS

looking something like "climatology_pi-0.8-win32.exe"

[seandepagnier]

Originally Posted by rgleason

If successful, you will find your packaged exe in this file
C:\o-plugin\climatology_pi\build\_CPack_Packages\win32\ NSIS

looking something like "climatology_pi-0.8-win32.exe"[/FONT]

Is there some reasoning for not packaging the data files? They should be there, but first you must extract them into the data directory (next to src) in the plugin directory. This would simplify the install, but maybe it's best separate? When I have multiple climatology datasets to choose from it they will have to be separate anyway.


Also.. could you post the notes you made on this process on the main site for other users to benefit?

[rgleason]

Sean I posted the Package process for windows in Sean's plugins thread and in Dev manual under compiling windows - sub page for plugins.

Sent from my SCH-I545 using Cruisers Sailing Forum mobile app

[seandepagnier]

I'm just waiting to hear from someone that rick's installer worked. Then will post the update to the main site, because the version on there is very old now.

[rgleason]

Is there some reasoning for not packaging the data files? They should be there, but first you must extract them into the data directory (next to src) in the plugin directory. This would simplify the install, but maybe it's best separate?

I just did not know better, still learning. Will do it the next time. I will be a bigger file but simpler install. For now, keeping it simple is better. When we get to different sized datasets, then we can worry about the choices. Maybe just have an exe installer for each type of dataset?

Did you notice my minor complaint that the installer always insists in creating an opencpn directory, even if you have directed it to a special install of opencpn like opencpn3.3.1731? It then makes a directory opencpn underneath that and puts the plugin in there, which is not correct.

This may happen with other plugins, ...don't know.

What I ended up doing was just deleting the OPENCPN at the end and it installed fine.

[rgleason]

Tonight after git pull weather_routing and successful cmake compiles and cpack,
did git clone for climatology_pi, then from a new build directory ran cmake .. and then cmake --build . and it came up with 17 errors. They look repetitive.
See attached please. Hope it is something simple. Thanks.

[rgleason]

Just git pull climatology, seemed to be changed files.
compiled and it had complaints similar to the one above. Please See attached.

[seandepagnier]

Rick,

I have made an update. Hopefully now it compiles.

[rgleason]

Sean,
At first there were errors at cmake --build . and cmake --build . --config release.
Then after copying version 3.3.1731 opencpn.lib file into ..climatology_pi/build/ it compiled properly. There was one warning, see below.

Build succeeded.

"C:\o-plugin\climatology_pi\build\ALL_BUILD.vcxproj" (default target) (1) ->
"C:\o-plugin\climatology_pi\build\climatology_pi.vcxproj" (default target) (4) -
>
(ClCompile target) ->
  ..\src\ClimatologyConfigDialog.cpp(260): warning C4800: 'long' : forcing value
 to bool 'true' or 'false' (performance warning) [C:\o-plugin\climatology_pi\bui
ld\climatology_pi.vcxproj]

    1 Warning(s)
    0 Error(s)
C:\o-plugin\climatology_pi\build>

I then used CPACK command to make an installer exe, with the data all setup in the climatology_pi folder under build, so the installer is 5+ plus but includes the data.

When execute the exe under advanced install, I still have to take off the Opencpn at the end!

Will test later.

[rgleason]

Climatology_pi works again! The sea depth isobar worked fine when I checked it.

Note: People using the plugin who insist on obsure things like contours for such things as sea depth or very close seatemp contours, must remember to minimize then maximize the program to get it to rewrite the screen, if the isobar progress bar seems to freeze. The plugin is very much better in this respect and I have not had a crash yet, I just use minimize program and maximize so the screen rewrites and the isobar progress bar has completed after I it maximize.

Thank you Sean. Now I need to get weather_routing going to do some tests.

[seandepagnier]

Originally Posted by rgleason

Climatology_pi works again! The sea depth isobar worked fine when I checked it.

Note: People using the plugin who insist on obsure things like contours for such things as sea depth or very close seatemp contours, must remember to minimize then maximize the program to get it to rewrite the screen, if the isobar progress bar seems to freeze. The plugin is very much better in this respect and I have not had a crash yet, I just use minimize program and maximize so the screen rewrites and the isobar progress bar has completed after I it maximize.

Thank you Sean. Now I need to get weather_routing going to do some tests.

Do you have an installer program I can put on sourceforge?

[rgleason]

Yes, Can I upload it to sourcefprge?

Sent from my SCH-I545 using Cruisers Sailing Forum mobile app

[rgleason]

Climatology_pi works again! The sea depth isobar worked fine when I checked it.

Note: People using the plugin who insist on obsure things like contours for such things as sea depth or very close seatemp contours, must remember to minimize then maximize the program to get it to rewrite the screen, if the isobar progress bar seems to freeze. The plugin is very much better in this respect and I have not had a crash yet, I just use minimize program and maximize so the screen rewrites and the isobar progress bar has completed after I it maximize.

Also DO NOT set Isobars on FINE, choose COARSE or NORMAL, unless you want to wait. NORMAL works and looks "fine".