Create installation Package.

[nohal]

Hans...
If I understood correctly, you build your own OpenCPN, so one that should sure work for you locally (but depending on your build may lead to a plugin DLL completely unusable by anybody else) is one of the build products you find in the Release/Debug subfolder of your build folder.
If you are not, there are some from our release builds at points where the API got significant additions at https://sourceforge.net/projects/ope...s/opencpn_lib/

Pavel

[hasse_A]

Yes I did. Problem is then, that the program crashes.
I now have built a plugin that works with 4.2.0.
It might have to do with the much higher data rate compared to gradar.
Or at least better. Will post a picture in my xHD radar thread.

/Hans

[nohal]

Well, you should use a debug build and see where it did crash and why, I'm afraid it will be a bit hard to debug from looking at a picture...

[hasse_A]

Actually, It has not crashed with the plugin used with the official release 4.2.0.
I do not saying that it wont. I will have to test more tomorrow.

The load on the computer does not seem to be the problem.
The load is around 20 % and opencpn takes about 10%.

What is needed to make an official release ?

/Hans

[nohal]

Originally Posted by hasse_A

What is needed to make an official release ?

/Hans

The release process for plug-ins generally looks like this:

1. You are reasonably sure your plugin works.
2. You tag a release corresponding to the version (same as the plugin actually reports through the API) in your Github repository
3. You send me an e-mail to the address you can find in my profile on Github (https://github.com/nohal)
4. I do the build for all our supported platforms and run a sophisticated set of tests on each of them (= your plugin does not crash immediately during startup, shutdown and about 10 seconds of completely random clicking around as any novice user without any clue what the plugin actually does would)
5. If 4) was a success, I upload the Windows and Mac packages to the CDN, launch the PPA builds and update the download page at opencpn.org. If 4) wasn't a success and the fixes needed are obvious, I send you a pull request with them and publish the release anyway. If the fixes need a lot of work or I'm not in a mood to work on them, I refuse to publish the release explaining why and steps 1-5 are repeated.
6. You are famous and the users happy.

Pavel

[rgleason]

Pavel, I find Hasse version clearer, but as you've noted before while workin on chartplotter, we use english a little differently.

Originally Posted by 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]

You guys edit the instructions to your liking. If it was just me, they would have not more than 10 lines.

Pavel

[hasse_A]

Ok. now that I have got some support for my idea I will change the manual.
Will do it when I have the time. I am a bit busy getting gxradar from crashing when closing OpenCPN.

/Hans