Posts: 2,184
Threads: 20
Joined: Jun 2016
Reputation:
64
Normally just use the master branch... I pushed a beta image for people to try out and it is using an unstable that is actually ahead of what is on github, sorry for any confusion. there are a lot of changes and I am not ready to make it the official release but it is close I think.
Posts: 102
Threads: 10
Joined: Apr 2021
Reputation:
0
Hello Sean, well understood. I will wait for your new release. Thank you again.
Eric
Posts: 2,184
Threads: 20
Joined: Jun 2016
Reputation:
64
I just didnt push those changes yet. I had some very difficult experiences the last few weeks so I am a bit out of touch.
Posts: 138
Threads: 2
Joined: Jul 2020
Reputation:
3
Hi John0047,
If you were be able to compile, you should have obtained a libpypilot_pi.so file. Just putting this file in the opencpn plugin path (/usr/local/lib/opencpn/ or something like that, just search where the other plugins so files are) should make the pypilot plugin available to opencpn.
Posts: 15
Threads: 1
Joined: Sep 2022
Reputation:
0
Hello Stelian
Tried that, opencpn crashes when pypilot_pi is selected. Just noticed that there is a large difference in the file size between the official versions and the one I built. Perhaps the build process was not as it should be however looked ok. I will have another attempt at the compile. John
Posts: 138
Threads: 2
Joined: Jul 2020
Reputation:
3
The difference is size is probably because your build has the debugging information included (it is not stripped). This is not the cause of the crash.
The cause of the crash is probably because the compile flags you used are different from the ones used for building opencpn. The easiest way is to look at how the "official" pypilot_pi from Cloudsmith is built (I think this comes from the Rick Gleason's pypilot_pi fork ?), and try to replicate the build process by yourself.