-
Notifications
You must be signed in to change notification settings - Fork 4
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
Building with make package
builds incompatible tarball
#8
Comments
It's probably because the local builds don't have any valid metadata. Check the tarball and see if the metadata has a valid download URL. Most likely it doesn't, because part of the "proper" build process using CircleCI calls cloudsmith-upload.sh, which IIRC does the metadata magic. Just curious, doesn't the engine dashboard appear in the plugin catalog ? |
It does not appear. Built O from (511ffcd)c8df63c43977ce94aabafb7e2515f60e4 yesterday. No Engine Dashboard in the plugin section available. |
I'm not running Debian Bookworm anywhere. What plugins are present in the catalog ? |
The compatibility is debian-arm64: as an example and the catalog master. |
Thanks, just need to work out what the other plugins are using/defining for their build scripts. With the release of OpenCPN 5.8, and switch to wxWidgets 3.2, all of the plugins had to be rebuilt with new dependencies and with specific tarball suffixes for them to appear in the catalog. It was painful to say the least. That was why for a long time, there was a lag before existing plugins began to appear in the catalog. For plugin developers it was like playing whack-a-mole |
Installed:
Not installed:
|
Done a manual build with
cmake -DWX_VER=32 ..
and thereafter
make && make package
The tarball cannot be installed via the import plugin feature from O. It just says error during installation.
If I copy the lib file and the data dir manually and enabling the pi in the config it works fine.
Done on Debian 12 (x86_64 Rpi 4)
Current Dev Version of O (5.9). I also had this issue earlier on.
The text was updated successfully, but these errors were encountered: