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

Create gradle build configuration #212

Open
4 tasks
Tracked by #197
rtibbles opened this issue Mar 28, 2024 · 0 comments
Open
4 tasks
Tracked by #197

Create gradle build configuration #212

rtibbles opened this issue Mar 28, 2024 · 0 comments

Comments

@rtibbles
Copy link
Member

rtibbles commented Mar 28, 2024

A big advantage of Chaquopy will be to make more of our build system more reproducible through Android Studio for dev purposes.

However, for the first pass integration it may be simpler to continue to do our custom unbundling/modifying of the Kolibri tar file outside of the scope of the Gradle build.

Therefore, for the first pass of Chaquopy build, we should be specifying the source of the installation for Kolibri from the patched tar file that we already create. Looking at the example for endless: https://github.com/endlessm/kolibri-installer-android/blob/develop/app/build.gradle.kts#L201 we would only install Kolibri, and do so differently, based on the patched tar source folder.

The endless build explicitly extracts migration folders to support Django's discovery. As this work will happen after Kolibri has been upgraded to Django 3.2, it is possible that this is no longer needed, but will need validation to be sure: https://github.com/endlessm/kolibri-installer-android/blob/develop/app/build.gradle.kts#L207

Lastly, looking at the example in the endless fork: https://github.com/endlessm/kolibri-installer-android/blob/develop/app/build.gradle.kts#L102 it seems that we do not need to support the x86 ABI, but should support the other three.

Tasks

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

No branches or pull requests

1 participant