-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TP Template Table #284
Comments
Main 5.8.0 Table OpenCPN/OpenCPN#2797 (comment) Same table under 5.8.0 Beta Dependency Discussions |
TP 1.0.230 Build List Revised and edited 4/8/2023 after Lennart's Issue with Jammy build. 1.0.230 - in cloudsmith testplugin-alpha |
Rick...
|
Dave.. (and Alec) Thank you. I've updated it and tried to simplify. O58 O56 are these ok now? |
Rick... O56: |
I think you may be right about that. Thanks for all your help and Alec's untangling my mess. |
Removed these from Debian 11 Buster wx32 |
Changed Debian 12 Bookworm (removing the wx32) from the file name Debian 12 Bookworm| | wx32 is assumed | |
Bdbcat review of the TP Template Table Logic: Production OCPN 58x on Bullseye is always wx30, whether for ARM(HF/64), or X86, a decision/plan made long ago. So there will be no instances of OCPN/Bullseye in the field that call for a wx32 target. The first time we target wx32 in ubuntu is Jammy. (Ubuntu 22.04). And also the largely equivalent Debian Bookworm. The reason the builds for Bullseye-wx32 fail is because there are no wx32 libraries available for Bullseye. Never have been any. While clever, trying to use the wx32 builds from jammy will not work, as these failed builds demonstrate. So, dropping Bullseye-wx32 from the Template table, and for the builds (as you have already done) is the right thing to do, after all. REMOVED Debian 11 Bullseye wx32| | wx32 version | |
Old NotesNotes:
|
The table has two entries for flatpak: flatpak-arm64 and flatpak-aarch64. aarch64 and arm64 are synonyms referring to the same hardware. We are using flatpak-aarch64 since the flatpak project uses the term aarch64. There is no such platform as flatpak-arm64 and this should thus be removed. OTOH flatpak-x86_64, the probably most used one is missing and should be added. EDIT: Either I got it wrong, or it it's fixed now. |
More remarks: the last line ubuntu-x86_64-2204-Jammy | Jammy | ubuntu-wx32-x86_64 | wx32 gtk3 KEEP Raspbian |
More: Debian bookworm plugins runs on Debian Bookworm and upcoming Ubuntu 24.04. Jammy runs bullseye (11) plugins. EDIT: That is not to say that the bullseye "version" is "Jammy", bulllseye is version 11 and nothing else. It targets some different platforms, one of which Jammy. |
Alec, thanks. From the table.. I can take the arm64 off, but it is just there for understanding and not used in reality.
Re:
@bdbcat I will let bdbcat comment as I don't do rpi. Re:
So you would like me to change the Version column from "Jammy" to "12 (Jammy, u24.04)"? |
No. It really depends on what you are trying to achieve. If it is about what plugins to use for Jammy you should replace "Debian 12 Bookworm" with "Debian 11 Bullseye" for all plugins targeting Jammy in the first column. The second column Version should read "11". If you want to make a note about that this one runs on Jammy, this belongs in the last Notes column That is, both Focal and Jammy runs Bullseye plugins. If it is about what the bookworm plugins does you should replace the Version column with "12" and add the targets Raspbian 12, Debian 12 and/or Ubuntu 24.04 in the Notes column. You can remove the gtk3 comments for 5.8, we don't build anything at all for gtk2 these days. |
Column 1 List of all unique builds required for all OS supported a given version of OpenCPN, with an adequately defined name to characterize it. Table covers O5.8 and O5.6.2 Table has 2 flatpak entries active for O5.8, one for flatpak-aarch64-2208 and the other for flatpak-x86_64-2208 Table does not have a single line under 05.8 for debian-11-bullseye (armhf, arm64, x86_64. My understanding is that these builds are for OpenCPN 5.6.2 only. Please explain because we will be dropping all builds under O5.6.2 pretty soon. I could make a separate column "Runs on" if you would prefer. Please explain what should be put in that column for all debian builds. Thanks Later: Have done some of this, but no idea if it is what you are suggesting. |
Short of time.
No. The bullseye plugins are used for for both Focal and Jammy as well as Debian 11/bullseye and Raspbian/11. In other words, these are probably the most used plugins as of today. OTOH, the bookworm/12 builds currently does not yet run on any Ubuntu LTS release; they will run on upcoming 24.04. However, the do run on Debian 12 and Raspbian 12. Stated otherwise, bookworm is the most recent release, not yet fully adopted everywhere. |
Dave Its more complicated than it needs to be I think. |
Rick....
Once again, jammy is the special case. Everything else in the O562 section can stay in place, frozon. |
Thanks. I thought that was what we needed to do, it makes more sense now, and when I drop O5.6.2 I won't drop all the Debian 11 Focal too! |
TestPlugin FE2 Template v1.0.278.11 in rgleason repos
OpenCPN 5.10.2 (running current O5.8 Plugins)
OpenCPN 5.6.2 Plugins Frozen - 28/05/2023
build-macos: Still building
build-msvc-2022: Still building
OpenCPN 5.8 Plugins
Generally these are still being maintained and built refer to the table above which represent the current builds.
Darwin-wx32-x86_64 is not needed because darwin-universal builds a compatible version.
Jammy is a special case. Under jammy, when OCPN is loaded from our launchpad repo, it uses wx32, but generic debian/11 provides only wx30. So a generic Debian /11 plugin will not work.
We need a special plugin build using debian 11 with wx32, which we do make as the special case.
OpenCPN 5.6.2 Plugins
Plugins using API 118 do not build these plugins.
If API=117 some of these are still being built.
Edited 4/10/2022 rgleason See Thread and subsequent discussion.
Edited 8/6/2023 Cleaned up unused. Moved Old Notes out to a post.
Edited 9/17/2023 Improved table to conform to comments.
Current build list for testplugin_pi
All by circleci, appveyor dropped because it no longer works.
@circleci-checks
View CircleCI workflow
OpenCPN 5.8 - This list is outdated insofar as Macos builds.
build-android-armhf - Success
build-android-arm64 - Success
build-flatpak-x86-2208 - Success
build-flatpak-arm64-2208 - Success
build-macos-wx32 - Success
build-msvc-wx32-2022 - Success
build-debian-x86_64-12-bookworm - Success
build-debian-arm64-12-bookworm - Success
build-debian-armhf-12-bookworm - Success
build-debian-armhf-11-bullseye - Success
build-debian-x86_64-11-bullseye - Success
build-debian-arm64-11-bullseye - Success
build-ubuntu-x86_64-2204-jammy - Success
OpenCPN 5.6.2
Note that Plugins using API 118 do not build these versions.
Some of these are still being built if API is 117
build-macos - Success
build-msvc-2022 - Success
build-debian-armhf-10-buster-gtk3 - Success
build-debian-arm64-10-buster - Success
build-debian-x86_64-10-buster - Success
build-debian-armhf-10-buster - Success
build-ubuntu-armhf-1804-buster - Success
NOTE: appveyor msvc wx312 build for OpenCPN 5.6.2 fails because it is missing a windows header. There will be one more run for OpenCPN 5.6.2 (without Windows), then all builds for OpenCPN 5.6.2 will stop. See
rgleason/watchdog_pi#66
Testing and Deployment
See #287
To ensure that we have a good template, because this is a complicated process, and we need to have some formalized steps & good testing So, before any publishing of plugins occurs:
Note: TP plugins built by rgleason will be re-built at 3 month intervals and longer if feasible.
The text was updated successfully, but these errors were encountered: