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

How does Buildozer handle libraries? #1835

Closed
mimmomarc opened this issue Jul 5, 2024 · 2 comments
Closed

How does Buildozer handle libraries? #1835

mimmomarc opened this issue Jul 5, 2024 · 2 comments
Labels

Comments

@mimmomarc
Copy link

Hi everyone, i'm new to using Buildozer. I think it's a very interesting and useful tool, it's fantastic!

I have a question,
for exampe, i have a project that uses a set of libraries, so i install them with

pip install library1 library2 library3

In the buildozer.spec file, i list the libraries i'm using :

requirements=library1,library2,library3

When you build the project, for example for Android, what does Buildozer do?
Does it make a copy of the installed libraries or does it generate new ones by retrieving and reinstalling them from a package source? Or something else ?

Thank you very much in advance

@RobertFlatt
Copy link
Contributor

You can read the log file to see the answer, but you got it right:

it generate new ones by retrieving and reinstalling them from a package source.

This is because the packages have to be for the version of Python used on Android which may or may not be the same as the local Python version, and also some packages are not pure Python and require compilation for Android as Android wheels do not exist in the repositories (this is what recipes are about).

There is as far as I know no official 'how it works' documentation.

Just driving by, I'm an occasional visitor don't expect a response.

Copy link

github-actions bot commented Dec 6, 2024

👋 @mimmomarc,
Sorry to hear you are having difficulties with Kivy's Buildozer; Kivy unites a number of different technologies, so building apps can be temperamental.
We try to use GitHub issues only to track work for developers to do to fix bugs and add new features to Buildozer. This issue has been closed, because it doesn't describe a bug or new feature request for Buildozer.
There is a mailing list and a Discord channel to support Kivy users debugging their own systems, which should be able to help. They are linked in the ReadMe.
Of course, if it turns out you have stumbled over a bug in Buildozer, we do want to hear about it here. The support channels should be able to help you craft an appropriate bug report.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants