oeSENC plug-in: New Version 1.6

[bcn]

A new version of the oeSENC plug-in is in place.
It corrects some smaller glitches.

The new Version 1.6 will be mandatory for oeSENC chart sets created in the future.
Chart sets issued starting from later this week or in the beginning of the next week will correct some more bugs concerning several "line"-objects and will allow us to compress the chart sets more. Resulting in smaller and faster downloads.
oeSENC 1.6 is fully backwards compatible with chart sets already in use.

Windows/Mac....Website links updated.
Linux.... PPA updated
Android.... Application Version 1.6 in full rollout now.

Please update your oeSENC plug-in as soon as possible!

Hubert

[Gilletarom]

Dave,

Not tested with charts but I have install oeSENC 1.6 on my new RPI3 with Debian Jessie and Openplotter.


Gilletarom.

[Gilletarom]

Hello Dave,


With my RPI, with OCPN 4.8, screen 10 inches.

I updated OpenCPN with Synaptic from O 4.6.1 (which is provided with openPlotter) to O 4.8.

I loaded a charts pack, France Atl, on o-charts today. Installation Ok.

The oeSENC charts are displayed.

Oups ... Sorry, Correction : No problem ... I see all objects (First, I write that this was not correct).

[Willem_Keizer]

Hi Hubert,

I updated openCPN from 4.6 to 4.8 today, as my oeSENC key was rejected in openCPN. Probably because I updated my openSuse Linux system. So I made a new fingerprint file and wanted to activate it on the o-charts site. There I noticed the remark on the update, so I decided to do a ful openCPN update. It installed all fine and runs well. There is only one issue, again on the oeSENC plugin: it sdoes not appear in the plugins list in openCPN. Maybe you can help me, I cannot find any hints on the internet. The log files provides the following message:

22:58:57 CET: PlugInManager searching for PlugIns in location /usr/lib/opencpn
22:58:57 CET: PlugInManager: Loading PlugIn: /usr/lib/opencpn/liboesenc_pi.so
22:58:57 CET: Error: /usr/lib/opencpn/liboesenc_pi.so: undefined symbol: _Z17glXGetProcAddressPKh
22:58:57 CET: PlugInManager: Cannot load library: /usr/lib/opencpn/liboesenc_pi.so

System I use is 64 bit openSuse Leap 42.3, kernel 4.4.104

It would be great if you could point me to a solution route.

Best regards,

Willem

[verkerkbr]

Originally Posted by Willem_Keizer

Hi Hubert,

I updated openCPN from 4.6 to 4.8 today, as my oeSENC key was rejected in openCPN. Probably because I updated my openSuse Linux system. So I made a new fingerprint file and wanted to activate it on the o-charts site. There I noticed the remark on the update, so I decided to do a ful openCPN update. It installed all fine and runs well. There is only one issue, again on the oeSENC plugin: it sdoes not appear in the plugins list in openCPN. Maybe you can help me, I cannot find any hints on the internet. The log files provides the following message:

22:58:57 CET: PlugInManager searching for PlugIns in location /usr/lib/opencpn
22:58:57 CET: PlugInManager: Loading PlugIn: /usr/lib/opencpn/liboesenc_pi.so
22:58:57 CET: Error: /usr/lib/opencpn/liboesenc_pi.so: undefined symbol: _Z17glXGetProcAddressPKh
22:58:57 CET: PlugInManager: Cannot load library: /usr/lib/opencpn/liboesenc_pi.so

System I use is 64 bit openSuse Leap 42.3, kernel 4.4.104

It would be great if you could point me to a solution route.

Best regards,

Willem

Beste Willem,

look at Synaptic and search for oesenc-pi and install it. I think that will work. Oesenc is no standard plugin.

Regards, groet,


Bram

[BlackSea]

Bram,

as you read, Willem has SuSE ( it's not Debian/Ubuntu). Synaptic is not available for SuSE. And SuSE uses RPM not DEB. It seems that function glXGetProcAddress not available on System

@Willem
Could you execute?

ldd /usr/lib/opencpn/liboesenc_pi.so

[stelian]

I had the same issue when compiling the plugin from git (on Ubuntu here). Reported it a while ago...

The fix:

diff --git a/src/oesenc_pi.cpp b/src/oesenc_pi.cpp
index c0333f6..8dbc4f3 100755
--- a/src/oesenc_pi.cpp
+++ b/src/oesenc_pi.cpp
@@ -2537,7 +2537,7 @@ static GLboolean QueryExtension( const char *extName )
 }
 
 typedef void (*GenericFunction)(void);
-void (*glXGetProcAddress(const GLubyte *procname))( void );
+extern "C" void (*glXGetProcAddress(const GLubyte *procname))( void );
 
 #if defined(__WXMSW__)
 #define systemGetProcAddress(ADDR) wglGetProcAddress(ADDR)

[Willem_Keizer]

Hi guys, thank you for your tips and help. From BlackSea's note I understand it may be a dependency issue, with does not seem unlikely. I have libepoxy0 installed, the library that seems to provide glXGetProcAddress

Stelion, I thought about compiling from git, but this is too complex for me. I used to get around with downloading and compiling using make etc., but the git-cloning thing I have not figured out yet.

BlackSea, I ran the command, the output is below.

Thanks again. Willem

~> ldd /usr/lib/opencpn/liboesenc_pi.so
linux-vdso.so.1 (0x00007ffd29fb1000)
libwx_baseu-suse-nostl.so.1 => /usr/lib64/libwx_baseu-suse-nostl.so.1 (0x00007fcce8236000)
libwx_gtk2u_core-suse-nostl.so.1 => /usr/lib64/libwx_gtk2u_core-suse-nostl.so.1 (0x00007fcce7aa6000)
libwx_baseu_net-suse-nostl.so.1 => /usr/lib64/libwx_baseu_net-suse-nostl.so.1 (0x00007fcce785e000)
libwx_gtk2u_html-suse-nostl.so.1 => /usr/lib64/libwx_gtk2u_html-suse-nostl.so.1 (0x00007fcce758e000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fcce71fe000)
libm.so.6 => /lib64/libm.so.6 (0x00007fcce6efe000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fcce6ce6000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fcce6ac6000)
libc.so.6 => /lib64/libc.so.6 (0x00007fcce671e000)
libz.so.1 => /lib64/libz.so.1 (0x00007fcce6506000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fcce62fe000)
/lib64/ld-linux-x86-64.so.2 (0x00007fcce89d6000)
libgtk-x11-2.0.so.0 => /usr/lib64/libgtk-x11-2.0.so.0 (0x00007fcce5cbe000)
libgdk-x11-2.0.so.0 => /usr/lib64/libgdk-x11-2.0.so.0 (0x00007fcce5a06000)
libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007fcce57f6000)
libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007fcce54ce000)
libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007fcce52a6000)
libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007fcce5056000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007fcce4dfe000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007fcce4aee000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fcce47ae000)
libXxf86vm.so.1 => /usr/lib64/libXxf86vm.so.1 (0x00007fcce45a6000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007fcce439e000)
libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007fcce415e000)
libjpeg.so.8 => /usr/lib64/libjpeg.so.8 (0x00007fcce3eee000)
libtiff.so.5 => /usr/lib64/libtiff.so.5 (0x00007fcce3c76000)
libmspack.so.0 => /usr/lib64/libmspack.so.0 (0x00007fcce3a5e000)
libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007fcce3856000)
libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007fcce364e000)
libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007fcce3426000)
libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007fcce309e000)
libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007fcce2e86000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007fcce2c46000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007fcce2a36000)
libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007fcce282e000)
libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007fcce261e000)
libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007fcce240e000)
libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007fcce21fe000)
libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007fcce1ff6000)
libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007fcce1dee000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007fcce1bd6000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007fcce1936000)
libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007fcce168e000)
libEGL.so.1 => /usr/lib64/libEGL.so.1 (0x00007fcce1456000)
libxcb-shm.so.0 => /usr/lib64/libxcb-shm.so.0 (0x00007fcce124e000)
libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007fcce103e000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fcce0e1e000)
libGL.so.1 => /usr/X11R6/lib64/libGL.so.1 (0x00007fcce0afe000)
librt.so.1 => /lib64/librt.so.1 (0x00007fcce08f6000)
libthai.so.0 => /usr/lib64/libthai.so.0 (0x00007fcce06e6000)
libffi.so.4 => /usr/lib64/libffi.so.4 (0x00007fcce04d6000)
libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007fcce0266000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007fcce0046000)
libuuid.so.1 => /usr/lib64/libuuid.so.1 (0x00007fccdfe3e000)
liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007fccdfc0e000)
libjbig.so.2 => /usr/lib64/libjbig.so.2 (0x00007fccdf9fe000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fccdf7d6000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fccdf5be000)
libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007fccdf32e000)
libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007fccdf0fe000)
libbz2.so.1 => /usr/lib64/libbz2.so.1 (0x00007fccdeeee000)
libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x00007fccdece6000)
libxcb-dri2.so.0 => /usr/lib64/libxcb-dri2.so.0 (0x00007fccdeade000)
libxcb-dri3.so.0 => /usr/lib64/libxcb-dri3.so.0 (0x00007fccde8d6000)
libxcb-present.so.0 => /usr/lib64/libxcb-present.so.0 (0x00007fccde6ce000)
libxcb-xfixes.so.0 => /usr/lib64/libxcb-xfixes.so.0 (0x00007fccde4c6000)
libxcb-sync.so.1 => /usr/lib64/libxcb-sync.so.1 (0x00007fccde2be000)
libxshmfence.so.1 => /usr/lib64/libxshmfence.so.1 (0x00007fccde0b6000)
libgbm.so.1 => /usr/lib64/libgbm.so.1 (0x00007fccddea6000)
libwayland-client.so.0 => /usr/lib64/libwayland-client.so.0 (0x00007fccddc96000)
libwayland-server.so.0 => /usr/lib64/libwayland-server.so.0 (0x00007fccdda7e000)
libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007fccdd866000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fccdd65e000)
libnvidia-tls.so.304.137 => /usr/lib64/tls/libnvidia-tls.so.304.137 (0x00007fccdd456000)
libnvidia-glcore.so.304.137 => /usr/lib64/libnvidia-glcore.so.304.137 (0x00007fccdb066000)
libdatrie.so.1 => /usr/lib64/libdatrie.so.1 (0x00007fccdae5e000)
libgraphite2.so.3 => /usr/lib64/libgraphite2.so.3 (0x00007fccdac36000)

[RalphG]

Willem,

I had the same issue with undefined symbol glXGetProcAddress when I tried to compile on Scientific Linux (same as RedHat/CentOS); Dave added an extra #include to the plugin source (which probably contains the same definition as stelian's patch), and now the plugin can be loaded. The fix is already contained in the git sources, so I would recommend to give it a try; here's what I did:

git clone https://github.com/bdbcat/oesenc_pi
cd oesenc_pi
mkdir build
cd build
cmake
make ..

Good luck!

Regards, Ralph

[sailorF54]

Originally Posted by RalphG

Willem,

I had the same issue with undefined symbol glXGetProcAddress when I tried to compile on Scientific Linux (same as RedHat/CentOS); Dave added an extra #include to the plugin source (which probably contains the same definition as stelian's patch), and now the plugin can be loaded. The fix is already contained in the git sources, so I would recommend to give it a try; here's what I did:

git clone https://github.com/bdbcat/oesenc_pi
cd oesenc_pi
mkdir build
cd build
cmake
make ..

Good luck!

Regards, Ralph

Correcting typing errors...

git clone https://github.com/bdbcat/oesenc_pi
cd oesenc_pi
mkdir build
cd build
cmake ../
make
sudo make install

optionally
sudo make package
if you want to keep a deb package...

[RalphG]

Originally Posted by sailorF54

Correcting typing errors...

Oh yes, thank you, of course cmake needs the parent directory.

Originally Posted by sailorF54

sudo make package
if you want to keep a deb package...

... which is unlikely on SuSE linux; if you want a RPM, you can edit the file 'CPackConfig.cmake' and replace 'SET(CPACK_GENERATOR "DEB;TBZ2")' by 'SET(CPACK_GENERATOR "RPM")'.

[Kjetil]

Hi.
My windows 10 just upgraded to the Fall Creator Edition (1709), and the oeSENC charts stopped working. Wrong UserKey is the message. Is it still a problem when there is a version upgrade? I’m running OpenCPN 4.8.2 and the oeSENC pi 1.6.

Thanks.

Kjetil

[bcn]

In general we did not notice problems with the latest W10 upgrades.

In order to analize your case please just create a new system with the actual SystemIdentifierFile (the fpr) to allow to compare the different system status.

And drop a notice at o-charts just to identify the action and the issue.

[Kjetil]

OK, I will.

I changed the WiFi card on this Laptop a few weeks ago. Can’t remember if I tested the oeSENC charts after that and before the W10 update. Maybe that explains it?

Kjetil.

[bcn]

If W10 updated we have most probably the "culprit".
But we need the fpr to be sure comparing with he previous situation.

Hubert