OS Raspberry specific RPI

[HUR450502]

Originally Posted by jongough

Looking at the logs it seems OCPN is using wxWidgets 3.0.4 and the plugins are built for 3.1.2, this may be the compatibility issue. What is the correct version of wxWidgets for arm64 flatpak?

jongough, that might be a solution... however, as mentioned earlier, I might need some support to get this fixed, can you possibly help me here?



Just for all who look into this here, this is currently MY testenvironment, so, if something gets wrong, no sweat, I can rebuild, etc.. however, I would like to get this running, to make use of the 64 bit architecture and be probably ready for any further developments here.



So, as said, I am not very skillid in these environments, but would be ready to provide any info and do tests, as you like or recommend, o.k.??


Thanks a lot for your help and understanding.



Best regards, Uwe

[rgleason]

Uwe, did you follow the rpi installationin opencpn manual?
See opencpn.org

[HUR450502]

Hi Rick,



yes I did, the Rpi 4 version using Flatpak.
I do not know, if I made something wrong there, however, it looked like the description.



As I said, I can redo all the things without problem as the system is not really in use yet, however, it ist interesting, that a number of the plugins seem to work - even the latest updates for o-charts were fine. If there sis a problem with the wxwidgets, as jongough suggested, how do I get a handle on them??



Best regards,



Uwe

[bdbcat]

@Rick...
Jon has the correct idea.



Looking at this specific problem:
System:

rpi/4
RaspiOS/Bullseye/64
Flatpak stable branch.


Consider one plugin: Climatology
The host system is built for wx3.0.
The plugin is built for wx3.1.
So, the plugin does not load.


Apparently, the Frontend in use has built this (and probably several other ) plugins for Flatpak using wx3.1. We have been experimenting with using wx3.1 on Flatpak, but this is not yet ready for release. It will not be used on O562 for flatpak. We will stay with wx3.0 for this platform.



So, that is the root of the instant problem.
Please have a look at the build scripts, and revert to wx3.0 in the Frontend. To stay focused on a reproducible case, start with one plugin (suggest climatology), get it working, and then update the rest one by one.



Thanks
Dave

[HUR450502]

Dear friends,



I do not know how many users have this problem. If I am the only one currently, then this is of no urgency, as I am just playing around with the 64 Bit thing. It looks to me however, that the problem might recur, if again different levels of the widgets are being used, so, besides redoing the plugins in question, it needs to be ensured, that all are working from the same platform ...

You see, I am sitting here, let you do the work and have "intelligent" comments. .... Sorry. .


I definitely want to thank you all for all the labour of love you are doing here, and I want to let you know, how much I appreciate this and this is a great product you have created!!


Thank you very much and my best regards,



Uwe

[rgleason]

Originally Posted by bdbcat

@Rick...
Jon has the correct idea.

Looking at this specific problem:
System: rpi/4
RaspiOS/Bullseye/64
Flatpak stable branch.

Consider one plugin: Climatology
The host system is built for wx3.0.
The plugin is built for wx3.1.
So, the plugin does not load.

..wx3.1 will not be used on O562 for flatpak. We will stay with wx3.0 for this platform.

So, that is the root of the instant problem.
Please have a look at the build scripts, and revert to wx3.0 in the Frontend. To stay focused on a reproducible case, start with one plugin (suggest climatology), get it working, and then update the rest one by one.

Too bad..rebuilding all the plugins again during a very busy time. I am sure everyone will understand it will take some time. I did start slowly!!! Climatology and others were updated sometime ago to TP 1.0.185. Nobody tested.

Should all the TP 1.0.194 plugins built for RPI Flatpak 64 Bullseye be removed now? -- That I can do very quickly.

As I recall, and I may be wrong about this, but I thought the timeline indicated that wx3.1 this was going to happen, ..but somehow somewhere the plans changed .. These kinds of changes are disruptive Jon's and my process. It would be very helpful if someone were to red flag these things direct to us. Fortunately there aren't many 64 bit Bullseye users, so I am not going to care too much.


Sorry, Uwe.

[bdbcat]

Rick...
"Should all the TP 1.0.194 plugins built for RPI Flatpak 64 Bullseye be removed now?"
Yes, probably best.


My recollection is that wx315 was proposed, and tentatively approved, for all platforms, post-O5.6.x. It was discussed and was understood that switching to wx315 for linux packages will cause immediate ABI breakage, so the switch was not to be taken lightly. Don't know how the Flatpak plugin workflow was migrated to wx31. Maybe to support initial testing of 315?



"Fortunately there aren't many 64 bit Bullseye users..."
Au contraire. New users of rPI/4 are most likely to install the latest available RaspiOS version available. And today, that is Bullseye/64. Flatpak is the recommended way to run OCPN on rPI Bullseye. We have no other native runtime solution supporting plugins for OCPN 5.6.x. on rPI/4/400 Bullseye/64


Rick, please do your best, and let me know how I can help.
Thanks
Dave

[mgrouch]

BBN Marine Linux OS for Raspberry Pi
2022-03-30-Release-Stable

Free and opensource.

Long Term Support Release 13.

Based on Buster

Changes:

AvNav updates
RPI firmware updates
SignalK and few plugins updates
Few stability fixes
Doc updates
Download at https://cloudsmith.io/~bbn-projects/...s/?q=lysmarine

Getting Started Guide: https://bareboat-necessities.github....reboat-os.html

Thanks

[rgleason]

Dave wrote:
Rick, please do your best, and let me know how I can help.

Ok, I'll try to get it done. There are a few main plugins that need some attention in terms of minor bugs, but I have released them anyway. If you could help solve those issues if Sean is not going to do it, would be very helpful.

[jongough]

By having aarm64 Flatpack use wx3.0 and then move to wx3.1 for the next OCPN version there now needs to be two new targets that specify the widgets version that has been used in the build. Without this we get a similar issue to the gtk2/gtk3 one that has caused issues and many rebuilds.

Can a standard be set for the use of XML/XSD and naming conventions including the, now complicated and inconsistent, target? We keep adding 'work arounds' for 'special cases' which makes the build scripts convoluted and having issues like this one.

[mgrouch]

Is wx with non even second positional numbers supposed to be a non-production release which official Debian would never use?

[HUR450502]

.... wow !!!!!!

Whoever did this, - I believe it was Rick who spent sleepless nights....
THANK YOU

It is impressive,to see your dedication and it makes me not feeling good to just throw such pack of work onto your table with a few questions.

Today I upgraded the catalog to the latest version and to my surprise and delight saw all the - now working perfectly - plugins which have been updated.



Again, thanks to you all, with my humble best wishes for the - hopefully - not so busy weekend....



Uwe

[rgleason]

Uwe, Thank you for your report. It is vital to get these kinds flags from you and other active users, otherwise we would not know there was a problem, as I certainly do not have every OS supported, nor do others.

As you can tell, it is best to catch these problems as early as possible in the process. So your "beta" testing is appreciated!

Very glad they are working. Please note there are still some known "bugs" in these plugins and several need some real TLC (tender loving care) by a real programmer who knows what he is doing! We are actively soliciting help in that respect.

The first plugin we need help with is Weather_routing!

[HUR450502]

Hi Rick,



for sure I cannot help with coding, but what is it you need for the weather-routing?



Best regards,



Uwe

[mgrouch]

Second Bullseye-based stable release of free and open source BBN Marine OS for Raspberry Pi is available for downloads.

This release is arm64 with noticeable improvements in performance.

There is number of new features (compared to previous Buster-based releases)

Better PyPilot support
Better Victron support
Few additional apps

Many included plugins for SignalK and OpenCPN

Fair Winds!

Download link:

https://github.com/bareboat-necessit...ag/v2022-09-11