Plugin Distribution

[rgleason]

Pavel and SethDart,
I have been compiling Sean's plugins and any others that use the Standalone system with success and I find it is much easier and simpler. Much of it is done by hand, but I have also made some batch files to help, but I don't find I use them that much. I do this for Windows:

1. All plugins reside in C:\..\Navigation\o-plugin
2. Opencpn.lib versions are kept in C:\..\Navigation\o-plugin\opencpn-lib
3. Under opencpn-lib I have opencpn-3.0.lib, opencpn-3.2.lib, opencpn-3.2.2.lib, opencpn-3.3.2017.lib <---whatever is the current beta
4. Then there is a folder for all the plugins created by the git clone....command.
5. I simply copy the appropriate opencpn-3.x.xxxx.lib to opencpn.lib under the build directory. The opencpn.lib often stays the same unless the Plugin API is changed.
6. In normal practice I go to the plugin folder and issue "git fetch" or :git pull"
7. Then compile under the build directory using cmake .. then cmake --build . then cmake --build . --config release then cpack to make the package executable. (I have a batch file for this, but don't tend to use it.)
8. Then I copy the exe file into another directory called C:\..\Navigation\o-plugin-pack and add a sequential letter to the plugin.
9. Then I upload it to Opencpn Beta File thingie under the appropriate folder based upon the Opencpn version numbering that the plugin is intended for.
10. Since we are only now supporting v3.2.2 plugins as earliest, I have a folder 3.2.2 PI Win which is always there. Opencpn Beta File Thingie rguser rgpass
11. Then I have a rolling directory for the latest beta.
12. Sometimes Pavel uses the exe for windows plugins.

I can understand how you would like to automate, but I could just keep doing this when needed, until you get to some other better process. I could also pack it all up in a zip file and upload if you want the system.

[rgleason]

Yes Seth Dart, I was looking for this information (I'd seen it briefly sometime ago).

AlexandreRio commented on Aug 20, 2013
https://github.com/SethDart/vdr_pi/pull/1
"Allows to build plugin as independent package"

"I recently created a devel package for OpenCPN, so that plugins can be built separatly. I patch yours, hope you'll enjoy it.
Please, see the wiki page and the build page, where the OpenCPN-devel package is."

https://en.opensuse.org/OpenCPN-build-plugins

Packaging of the plugins
You juste have to add these two lines in your spec file and, if case of a conflict with libwx, specify the wanted package provider for libwx_baseu and libwx_gtk2u.

He has developed a system for OpenSUS

Can Windows, other flavors of Linux and OS X be added somehow?

[rgleason]

Well, I tried a standalone compile under windows of VDR, first doing a git clone, then copying opencpn-3.2.2.lib to a new directory /build/opencpn.lib

After put opencpn.lib (from version 3.2.2) in a new "build" folder and type cmake ..
..\vdr_pi\build>cmake ..
-- *** Building vdr_pi ***
CMake Error at CMakeLists.txt:57 (INCLUDE):
include called with wrong number of arguments. Include only takes one file.

CMake Error at CMakeLists.txt:77 (ADD_DEPENDENCIES):
add_dependencies called with incorrect number of arguments
-- Configuring incomplete, errors occurred!

In CMakeLists.txt
Line 57 INCLUDE(${wxWidgets_USE_FILE})

Line 77
IF(WIN32)
SET(OPENCPN_IMPORT_LIB "../../${CMAKE_CFG_INTDIR}/${PARENT}")
TARGET_LINK_LIBRARIES( ${PACKAGE_NAME} ${OPENCPN_IMPORT_LIB} )
ADD_DEPENDENCIES(${PACKAGE_NAME} ${PARENT}) <---Line 77
ENDIF(WIN32)


Also these are the dependencies in the various files. I believe these need to be in the Package to compile as standalone.

vdr_pi.h
-----------
#include "wx/wxprec.h"

#include <wx/fileconf.h>
#include <wx/filepicker.h>
#include <wx/file.h>
#include <wx/aui/aui.h>
#include "../../../include/ocpn_plugin.h"

vdr_pi.cpp
-------------
#include "wx/wxprec.h"
#include <typeinfo>
#include "vdr_pi.h"
#include "icons.h"

icons.sh
--------------
Require icotool from package icoutils
# Require convert from package ImageMagick
# Require inkscape

# 32x32

Has a path to create the icon
$path/../../../src/bitmaps/png2wx.pl -C $path/icons.cpp -H $path/icons.h -M ICONS_H $path/*.png


icons.h
--------------
#include <wx/wxprec.h>
#ifndef WX_PRECOMP
# include <wx/wx.h>
#endif

icons.cpp
---------------
#include <wx/wxprec.h>
#ifndef WX_PRECOMP
# include <wx/wx.h>
#endif
#include <wx/mstream.h>
#include "icons.h"

So anyway that was a neophyte's effort to change it to standalone.

[rgleason]

Re-read Pavel's email, which made reference to the git pull command below...
in a effort to get VDR packaging working...

from Run > Cmd
cd to ../o-plugin/vdr_pi
git pull https://github.com/nohal/vdr_pi packaging
downloads Pavel's packaging

cd build
cmake ..
1 Error ...missing ..buildwin/curlib.lib

See attached file for the 16 errors please. There are linkage errors.

[Hakan]

Pavel et.al....
A friend have got me, who have used Win since early Dos, to run Linux, Ubuntu for the first time. If I excuse my own history I would say it seems handy!?
But when I want t use the Plugins packages and use the: "sudo dpkg -i <packagename>.deb" what is the <packagename> for each plugin, or for example for WMM??
Thanks
Håkan

[nohal]

Hakan...
"<packagename>.deb" is the name of the file you just downloaded, so for the current version WMM one of wmm_pi_0.8-1_i386.deb, wmm_pi_0.8-1_amd64.deb or wmm_pi_0.8-1_armhf.deb, depending on your platform (X86 32bit, X86 64bit, ARM).

Pavel

[delatbabel]

Hi all,

I've been following along on this thread because I've taken over the development of the Logbook_konni plugin from konnibe who is too unwell to continue.

I now have the plugin building out of the OpenCPN source tree and will work on packaging shortly.

At some point I would like to get the plugins page entry for this plugin updated. the plugins page is here:

PlugIns | Official OpenCPN Homepage

The page redirects me to the plugins guidelines here:

PlugIn Guidelines | Official OpenCPN Homepage

That page contains a link at the bottom which says Plugin Submission Form, here:

PlugIn Submission Form | Official OpenCPN Homepage

That form is blank.

Any clues?

Del

[rgleason]

Del wrote:

At some point I would like to get the plugins page entry for this plugin updated.

Best thing to do is to register yourself here
User account | Official OpenCPN Homepage

Then login and start slowly...

the plugins page is here:
PlugIns | Official OpenCPN Homepage

This is the Plugins Download page
Pavel edits this page, you do not have access to it.
Pavel will add/edit what he thinks is appropriate.

The page redirects me to the plugins guidelines here:
PlugIn Guidelines | Official OpenCPN Homepage

This page is under the Developer's Manual
As a developer you might want to know the guidelines?
No need to edit at this point except for greater clarity.

That page contains a link at the bottom which says Plugin Submission Form, here:
PlugIn Submission Form | Official OpenCPN Homepage
That form is blank.

This is also for Developers! but your plugin has already been submitted and accepted.

Where you want to edit and improve the Plugin Manual is in the
"Opencpn User Manual" which is at the top of the left panel, and goes here to
OpenCPN User Manual | Official OpenCPN Homepage
Then below Advanced features pick plugins
Plugins | Official OpenCPN Homepage

I note that there is no page started for Logbook Konni! Perhaps the first thing to do is to create a new page and get it listed, then start Adding instructions for using the plugin along with uploading screen shots to help.

Adding the first page and getting into the outline can be a bit of a trick the first time, so if you are having trouble, let me know and I can start you out with a new page. ..I will not be available to do this tomorrow, but maybe the next day..

Thanks Del. I hope that others will give Del a big assist with documentation for Konni's Logbook. Its much easier if several people work together, as we did for the Celestial Nav pages, its actually quite fun and productive creating a good instruction page. Any volunteers to help Del?

[rgleason]

Del,
I just added the page that can be edited (it is not at all hard to do as long as you first go to the summary list of plugins and select "Add a child page").

[But do NOT try to create a page and insert it in the outline, that is much harder.]

I think you will be too busy with programming and responding to things, to actually write up the plugin and I would like to suggest that some ardent logbook users take this opportunity to give us a big help!

[delatbabel]

Thanks rgleason.

What I was trying to do was to get the plugins page edited so that the entry on that page for Logbook-konni could point to the new release from github and not konnibe's now obsolete release. I was hoping that there was a submission form that would go to the page admin.

I see that Logbook-konni already has an entry on that page, I want that entry modified. I guess konnibe has the password for it, however he has been incapacitated with a stroke and so no longer able to contribute or update the page.

I am quite happy with doing documentation when the time comes but all contributions welcome of course.

There have already been several stability and functionality changes made to the logbook plugin and we're nearly but not quite ready for a release. I am waiting on packagers and testers for the platforms I don't have (MacOS and Windows) to get back to me on their results. What I could use help with is packaging although I'm looking through Dave's s63_pi plugin to see what I can port across.

Del

[Taarnskov]

I would be happy to test if you could give me access to a windows version

Regards, Lars

[delatbabel]

Originally Posted by Taarnskov

I would be happy to test if you could give me access to a windows version

Regards, Lars

Best I can suggest is to grab the source from github and compile according to the instructions here:

https://github.com/delatbabel/LogbookKonni-1.2

I don't have a compiler for Windows. I have a windows system but I can't build the plugin on it without the compiler.

Del

[rgleason]

Lars I can try to compile a windows version tomorrow. Traveling today.
Del, I wrote Pavel a short note to see I he can update the links.

What about Findit? Will you be the parent/dev?

[Taarnskov]

Rick, It would be nice to test and Comment the New version for windows.
Lars


Send from my IPad

[seandepagnier]

Originally Posted by delatbabel

I have a windows system but I can't build the plugin on it without the compiler.

You can download the compiler.