New Plugin Development on Linux

[globalkeith]

So I've started looking at how to create a new plugin, so I've copied "demo_pi" to a new directory and renamed everything accordingly.

Everything builds ok, however when I do "sudo make install" (on Ubuntu 12.04) the .po file is copied to:

/usr/local/share/opencpn/plugins/liblatlonbounds_pi.so


Whereas all the other plugins get copied to:

/usr/local/lib/opencpn/libgrib_pi.so


Is this something I've done wrong, or does the demo_pi need updating?

[bdbcat]

keith...

Bingo!

demo_pi is out of date.
If you can patch it to move the install location to the proper place, I'll include that in the next Beta.

Or, just copy it it you want to fool around with it.

Thanks, and welcome aboard
Dave

[globalkeith]

No probs, thanks D

[globalkeith]

Ok so its copying my plugin into the correct location: (My plugin is nothing more than a copy of the demo_pi_sample)

/usr/local/lib/opencpn/liblatlonbounds_pi.so

BUT its not showing up in the Plugins section of the preferences panel. There's no logs that suggest theres a problem - any suggestions as to what to do next? I've managed to compile the VDR plugin, so should I look to strip that down and use as a template instead?

thanks
keith

[nohal]

keith...
In https://github.com/ktec/OpenCPN/blob...lonbounds_pi.h change

#define     MY_API_VERSION_MINOR    1

to

#define     MY_API_VERSION_MINOR    5

the demo_pi code is really unmaintained for some time - consider using some normal plugin as your guide to plugin development. https://github.com/nohal/wmm_pi is really small and easy to understand for example.
Also, if you don't mind, please create a separate repository for your plugin and don't use a branch in the OpenCPN repo - I know it was my own invention, but the number of non-core plugins was 1 or 2 at that time and I was more or less the only person writing them. The idea was definitely not good - it actually starts to be a nightmare having so many remotes with a handful branches each connected to a single local repo just to get access to the plugins they contain...

Pavel

[rooiedirk]

Keith, Dave,
Looks like we running into the same problem at he same time.
I did some patching on the Demo plugin. Works now for me under linux.
It is using the PI API 1.8 now.
wkr
Dirk