STANDALONE PLUGINS - Compilation and use of Opencpn
For my benefit and others. What are the standards so I do not have to do it wrong.
1. I believe Pavel has said he is going to drop support for the 3.0 plugins.
What does this mean? --Going forward, we will not compile any moree 3.0 plugins, but the old ones will be hosted on the website download?
--Therefore, what happens if some of those have been changed, do they just get compiled with the opencpn
.lib of oldest stable version currently being supported?
2. With regard to Opencpn v 3.2 -Sean has said that we should be supporting the most recent stable version of that which is v3.2.2.
--So I had been compiling those plugins with opencpn.lib v3.2.0 (attached)
git checkout "opencpn-3.2.0" cf69568
--Should I be using opencpn.lib v3.2.2 (attached) instead for all Opencpn 3.2 plugins?
--Shouldn't ALL the plugins on the download website be compiled for v3.2.2?
--Shouldn't the title on the website read v3.2.2 rather than v3.2 to be clear?
PlugIns | Official OpenCPN Homepage
"Plugins for OpenCPN 3.2 and later:
--Also is the opencpn.lib for v3.2 the same as v3.2.2?
Process to get the respective opencpn.lib files
on May 7, 2013 opencpn-3.2.2 … 0c4bcc9
git checkout 0c4bcc9
Head is not at 0c4bcc9 3.2.2
git branch -v
* no branch 0c4bcc9 3.2.2
opencpn-3.2.0 cf69568 3.2.0
git checkout -b opencpn-3.2.2
cmake --build .
cmake --build . --config release
then search on opencpn.lib and find two
both the same 59kb
copy one to opencpn-lib folder
Also did the same for
git checkout -b opencpn-3.2.0
Have included this opencpn-3-2.lib too, but they appear to be the same size.
These files are attached for reference with the version number in them.
Should these be put up on the download website for others to use?
opencpn-3-2.lib (may not be needed or used)
These are binary files, please take the doc off. They are normally all designated "opencpn.lib" for the respective version of Opencpn.
For the standalone plugins they need to be copied into the build directory.