Create installation Package.

[hasse_A]

I am trying to install NSIS and if you read the manual "Compiling Windows" the installation should add "HKEY_LOCAL_MACHINE\SOFTWARE\NSIS" to the registry.
This does not happen. There is no such key.
There is however a key "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NSIS"
I have a 64 bit machine.
Maybe the manual should be updated or have I missed something ?

[nohal]

hasse_A...
Yes, if you have a 64bit version of Windows, the key is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NSIS instead.
FWIW, if your cmake version is "new enough", the bug this copy operation works around seems already fixed and it is not needed at all anymore. Documentation updated to hopefully cover all possible situations a person trying to follow the instructions can possibly be in.

Pavel

[hasse_A]

Thanks Pavel.
Am am stunned. You are fantastic.
/Hans

[hasse_A]

I think there is an ambiguity in the Developers manual.
I am using Windows.

Under "4. Build OpenCPN"
It says "CD into your the topmost source directory and create a directory named build under it:"

Now that can, as I see it, be either under .....\OpenCPN or under ....\OpenCPN\src. Which is it ?

/Hans

[nohal]

Hans...
Really? Do you think that a clarification as "Topmost directory is the topmost directory, not the src subdirectory" is necessary? Feel free to update the instructions, IMO this would already be a bit too much.

Pavel

[hasse_A]

Just leave out the words your and source.

"CD into the topmost directory and create a directory named build under it:"

Then I think it's obvious. No one would think it's under C:\

/Hans

[nohal]

Originally Posted by hasse_A

Then I think it's obvious. No one would think it's under C:\

That's what I'm really not sure...

[hasse_A]

Ok, Maybe it can be written like this then.

"CD into the topmost directory. i.e. under OpenCPN and create a directory named build under it:"

[nohal]

Hans...
For me it is really not any more comprehensible than what there is now. But as I said, feel free to rephrase the instructions.

Pavel

[hasse_A]

I won't change anything as what is not obvious for me might be for others and
I may risk making it less obvious for them.

/Hans

[Viking Sailor]

You could show an example...

[hasse_A]

Now I have managed to create an installation package for OpenCPN.

I will now try to create an installation package for the Garmin xHD radar plugin.

[hasse_A]

I have created an installation package for the gxradar plugin but
I get the error message that my plugin is not compatible with my 4.2.0
version of OpenCPN.
Now, could it be that I have used a version of wxWidget that is to new?
I have version 3.1.0 installed.
And might this be the only reason or are there other issues?

/Hans

[nohal]

Hans...
The reasons can be numerous. The plugin and the core program of course must use the same version of wxWidgets, you can't mix Release and Debug builds of core and plugins, the plugin has to be linked against opencpn.lib version <= the ABI of your OpenCPN core program, etc.
The logfile should contain a message explaining why the program refused to load the plugin DLL and whether it found it at all.

Pavel

[hasse_A]

Thanks Pavel!

I am at the moment fixing the wxWidgets to version 3.0.2.
How do I know what version of opencpn_lib to use and where to find it ?

/Hans