Skip to content

Releases: maltfield/cross-platform-python-gui

Public Build Artifact: Windows 241416612

06 Sep 06:55
7ad1851
Compare
Choose a tag to compare
switching to pip install directly in AppImage

The previous solution of doing the `pip install` with the system's python, then rsync'ing into the AppImage had a couple issues:

 1. It was overwriting bin/python3.7 with a symlink back outside the AppImage, totally defeating the purpose of the AppImage and causing issues with systems that don't have python3.7 installed (see https://github.com/maltfield/cross-platform-python-gui/issues/4)

 2. It means that the system must have the same python version as the python version that's in our base python AppImage

I'm attempting to do this the proper way, but it's currently failing on my local system with this error:

	+ /tmp/appimagetool.AppImage /tmp/kivy_appdir dist/helloWorld.AppImage
	appimagetool, continuous build (commit effcebc), build 2084 built on 2019-05-01 21:02:41 UTC
	WARNING: appstreamcli command is missing, please install it if you want to use AppStream metadata
	Using architecture x86_64
	/tmp/kivy_appdir should be packaged as dist/helloWorld.AppImage
	AppStream upstream metadata found in usr/share/metainfo/python3.7.8.appdata.xml
	Generating squashfs...
	Parallel mksquashfs: Using 4 processors
	Creating 4.0 filesystem on dist/helloWorld.AppImage, block size 131072.
	[===========================================-                  ] 3820/5306  71%
	FATAL ERROR:gzip uncompress failed with error code -3
	Embedding ELF...
	Not able to open the AppImage for writing, aborting

I'm hoping that this is a memory-bound issue and it will "just work" on the GitHub shared runner cloud *fingers crossed*

 * https://github.com/AppImage/AppImageKit/issues/398#issuecomment-421107262

Public Build Artifact: Mac 241416612

06 Sep 06:54
7ad1851
Compare
Choose a tag to compare
Pre-release
switching to pip install directly in AppImage

The previous solution of doing the `pip install` with the system's python, then rsync'ing into the AppImage had a couple issues:

 1. It was overwriting bin/python3.7 with a symlink back outside the AppImage, totally defeating the purpose of the AppImage and causing issues with systems that don't have python3.7 installed (see https://github.com/maltfield/cross-platform-python-gui/issues/4)

 2. It means that the system must have the same python version as the python version that's in our base python AppImage

I'm attempting to do this the proper way, but it's currently failing on my local system with this error:

	+ /tmp/appimagetool.AppImage /tmp/kivy_appdir dist/helloWorld.AppImage
	appimagetool, continuous build (commit effcebc), build 2084 built on 2019-05-01 21:02:41 UTC
	WARNING: appstreamcli command is missing, please install it if you want to use AppStream metadata
	Using architecture x86_64
	/tmp/kivy_appdir should be packaged as dist/helloWorld.AppImage
	AppStream upstream metadata found in usr/share/metainfo/python3.7.8.appdata.xml
	Generating squashfs...
	Parallel mksquashfs: Using 4 processors
	Creating 4.0 filesystem on dist/helloWorld.AppImage, block size 131072.
	[===========================================-                  ] 3820/5306  71%
	FATAL ERROR:gzip uncompress failed with error code -3
	Embedding ELF...
	Not able to open the AppImage for writing, aborting

I'm hoping that this is a memory-bound issue and it will "just work" on the GitHub shared runner cloud *fingers crossed*

 * https://github.com/AppImage/AppImageKit/issues/398#issuecomment-421107262

Public Build Artifact: Linux 241416612

06 Sep 06:53
7ad1851
Compare
Choose a tag to compare
Pre-release
switching to pip install directly in AppImage

The previous solution of doing the `pip install` with the system's python, then rsync'ing into the AppImage had a couple issues:

 1. It was overwriting bin/python3.7 with a symlink back outside the AppImage, totally defeating the purpose of the AppImage and causing issues with systems that don't have python3.7 installed (see https://github.com/maltfield/cross-platform-python-gui/issues/4)

 2. It means that the system must have the same python version as the python version that's in our base python AppImage

I'm attempting to do this the proper way, but it's currently failing on my local system with this error:

	+ /tmp/appimagetool.AppImage /tmp/kivy_appdir dist/helloWorld.AppImage
	appimagetool, continuous build (commit effcebc), build 2084 built on 2019-05-01 21:02:41 UTC
	WARNING: appstreamcli command is missing, please install it if you want to use AppStream metadata
	Using architecture x86_64
	/tmp/kivy_appdir should be packaged as dist/helloWorld.AppImage
	AppStream upstream metadata found in usr/share/metainfo/python3.7.8.appdata.xml
	Generating squashfs...
	Parallel mksquashfs: Using 4 processors
	Creating 4.0 filesystem on dist/helloWorld.AppImage, block size 131072.
	[===========================================-                  ] 3820/5306  71%
	FATAL ERROR:gzip uncompress failed with error code -3
	Embedding ELF...
	Not able to open the AppImage for writing, aborting

I'm hoping that this is a memory-bound issue and it will "just work" on the GitHub shared runner cloud *fingers crossed*

 * https://github.com/AppImage/AppImageKit/issues/398#issuecomment-421107262

Public Build Artifact: Windows 236469280

02 Sep 17:41
7408659
Compare
Choose a tag to compare
236469280_windows

adding link to demo executables

Public Build Artifact: Mac 236469280

02 Sep 17:41
7408659
Compare
Choose a tag to compare
Pre-release
236469280_mac

adding link to demo executables

Public Build Artifact: Linux 236469280

02 Sep 17:39
7408659
Compare
Choose a tag to compare
Pre-release
236469280_linux

adding link to demo executables

Public Build Artifact: Windows 214903341

19 Aug 08:46
be7c8db
Compare
Choose a tag to compare
making linux AppImages available locally instead of downloaded at bui…

…ld time

The last build failed because our python3 AppImage 404d on download. For buskill-app (the first repo that cloned *this* repo as a cross-platform GUI python app), I ended up making all dependencies download locally--well, just the ones outside apt that can't be downloaded securely.

 * https://github.com/BusKill/buskill-app/issues/2

For now this commit just copies some of that logic upstream to this repo so that the linux builds won't fail due to 404 in the future..

Public Build Artifact: Mac 214903341

19 Aug 08:44
be7c8db
Compare
Choose a tag to compare
Pre-release
making linux AppImages available locally instead of downloaded at bui…

…ld time

The last build failed because our python3 AppImage 404d on download. For buskill-app (the first repo that cloned *this* repo as a cross-platform GUI python app), I ended up making all dependencies download locally--well, just the ones outside apt that can't be downloaded securely.

 * https://github.com/BusKill/buskill-app/issues/2

For now this commit just copies some of that logic upstream to this repo so that the linux builds won't fail due to 404 in the future..

Public Build Artifact: Linux 214903341

19 Aug 08:43
be7c8db
Compare
Choose a tag to compare
Pre-release
making linux AppImages available locally instead of downloaded at bui…

…ld time

The last build failed because our python3 AppImage 404d on download. For buskill-app (the first repo that cloned *this* repo as a cross-platform GUI python app), I ended up making all dependencies download locally--well, just the ones outside apt that can't be downloaded securely.

 * https://github.com/BusKill/buskill-app/issues/2

For now this commit just copies some of that logic upstream to this repo so that the linux builds won't fail due to 404 in the future..

Public Build Artifact: Windows 205109907

12 Aug 06:12
ec275a1
Compare
Choose a tag to compare
attempting to add --force-reinstall to fix downstream ModuleNotFoundE…

…rror issues:

 * https://github.com/maltfield/cross-platform-python-gui/issues/1