Skip to content
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

[FeatureRequest] VirtualMachine images with mobile cross compilation environments ready for use. #1593

Open
cederom opened this issue Apr 14, 2023 · 3 comments

Comments

@cederom
Copy link
Contributor

cederom commented Apr 14, 2023

Hello world :-)

As I have serious problems with cross-compilation of kivy application to Android and iOS (none of them works at this time), I have tried Linux LUbuntu, Linux Debian, macOS 12 x86, macOS 13 M1, also Docker does not seem to work (gives the same results as bare metal).

This cross compilation already introduced around month of delay in application deployment and development. This can jeopardize Kivy as the solid cross platform development framework.

I would like to propose creating rock solid working out-of-the-box virtual machine images that would be ready to use for a cross compilation to Android and iOS.

Creating vm images with Linux seems trivial. This will result in better solution than Docker as I could use such image on FreeBSD, macOS, Windows, etc.

I know that macOS is licensed only to run on Apple hardware, and may be hard to accomplish, but it would be also nice to have if possible.

Thanks for considering :-)
Tomek

@Julian-O
Copy link
Contributor

There is already a Packer virtual machine: https://github.com/kivy/buildozer/tree/master/buildozer/tools/packer

@cederom
Copy link
Contributor Author

cederom commented Oct 25, 2023

Thanks @Julian-O this packer based solution seems obsoleted long time ago. Not quite what I was describing. I obtained new macOS build machine just to get things working faster. Maybe GitHub/GitLab actions would be more of use here and also support macOS/iOS builds?

@Julian-O
Copy link
Contributor

this packer based solution seems obsoleted long time ago.

Ok, we need clarity on that.

#1663 is about getting clarity about Docker. This may need a similar ruling - get it up to scratch or cull it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants