Hi Tony et al
I have a some experience with pyinstaller and linuxdeploy to release multi-platform tools in other projects (Win + Lin + Mac) as an quasi standalone app; with some tweaks you can make it work flawlessly, the trick is to use the lowest version kernel available, being the "standard" the latest LTS version of the OS, in Ubuntu ecosystem that's 16.04
The trick is the libc version and the full backwards compatibility of new version with older ones, with time and testing maybe using 14.04 as base will fill all the gaps
I can try to play with it locally and then with travis-ci for the automation process
I'm eager to see/test the flatpack script, can anyone point me to it?
IMHO the appimage format is better than flatpack/snap in this scenario, as it's 100% portable, aka: no need to install anything or tied to a particular distro/version if created wisely
I will be testing the two variants, pyinstaller & appimage, as usual, little free time, but I will keep the list posted on any advance and will be grateful of feedback on tests.
Cheers, Pavel
El 3/7/20 a las 14:38, Tony Fuller escribió:
Hi Pavel,
Don't forget Ubuntu Focal is only one of many distributions affected by the python2 support drop.
Things may have changed but when I played with pyinstaller before I found the resulting executable was not compatible across Ubuntu versions (i.e. a executable created on 18.04 wasn't compatible with 16.04 etc.) Some variations may work but I think the dynamic link to glibc was one root cause. What this implies is the build system needing to run the script on multiple OS roots (in a docker/chroot/VM) which would then output a number of executable files. Linux users would have no issue downloading the correct version but the build system doesn't scale when you include other distributions (suse/fedora/Debian/etc). Maybe there's an advanced option I missed in pyinstaller to resolve those issues.
I still think using flatpak or snap is a better way to unify the currently fragmented Linux support. There already exists a working flatpak script, I have not see any Snap build scripts yet.
I'm happy to chat more about unifying Linux support for CHIRP too. Let me know if you find the same results.
Tony
*From:* chirp_devel-bounces@intrepid.danplanet.com chirp_devel-bounces@intrepid.danplanet.com on behalf of Pavel Milanes Costa (CO7WT) via chirp_devel chirp_devel@intrepid.danplanet.com *Sent:* Friday, July 3, 2020 1:23:00 PM *To:* chirp_devel chirp_devel@intrepid.danplanet.com *Subject:* [chirp_devel] "Success" to port Chirp as a stand alone app for Ubuntu Bionic... Hi, playing here with pyinstaller and at first glance I managed to run latest chirp from the hg repository.
See here https://pasteboard.co/JfYqbrL.png for a pic of it.
There are warnings in the import with some modules, but that must be a few hours of work to make it happy.
That's build on a Ubuntu 18.04 lxc image and crafted with pyinstaller (there are other options) packed as a really standalone app (just give exec permissions and fire it, no dependencies or other installs)
Is there a solution like this already?
It worth to work on this pro provide a way for the Focal users?
I can at the end provide a script or a recipe to build it on any of the free platforms out there (travis, etc)
Cheers, Pavel.
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers