Proposal: Android-Specific Metadata Support in Recipes

Introduce support in python-for-android to parse Android-specific metadata from pyproject.toml of pip-installed packages. This enables modular bundling of assets into APK builds, allowing packages to contribute platform-native components directly.

Example pyproject.toml Layout

[tool.python-for-android.android]
src = "android/src/"
res = "android/res/"
extra_manifest_xml = "android/extra_manifest.xml"
extra_manifest_application_xml= "android/extra_manifest_application.xml"
activities = [
    {
        "name": "org.package.android.MyActivity",
        "process": ":package_process",
    }
]
proguard = "android/proguard-rules.txt"
jniLibs = "android/jni/"
assets = "android/assets/"
resources = "android/resources"

etc. Etc.

How It Works

• During dependency resolution (p4a.recipe or pip stage), check for [tool.python-for-android.android] in pyproject.toml.
• Resolve declared paths from the site-packages directory.
• Inject collected files into dists/<your_app>/build/ before Gradle build.

Please consider this.

THANKS!!

Empieza leyendo el flujo de resolución de dependencias alrededor de p4a.recipe o de la fase de pip, y después inspecciona cómo se gestionan actualmente los metadatos de pyproject.toml y las rutas de site-packages. Sigue el recorrido de los archivos que entran en dists/<your_app>/build/ antes de la compilación de Gradle. Se considerará terminado cuando exista un diseño acordado y un camino de implementación para recopilar los metadatos de Android declarados e incluirlos en las compilaciones de APK.