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

[FR] Investigage cps support #186

Open
madebr opened this issue Sep 5, 2024 · 1 comment
Open

[FR] Investigage cps support #186

madebr opened this issue Sep 5, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@madebr
Copy link

madebr commented Sep 5, 2024

Is your feature request related to a problem? Please describe.

The prefab json format is not very common, and its abilities are somewhat limited.
The Common Package Specification format might be a useful alternative to the prefab module json files.
CMake has experimental support for automatically generating cps files.

Describe the solution you'd like

Prefab defines a standard location where to store .cps files in aar-chives,
and can ingest .cps files, and generate ndk-build/cmake files based on this.

In CMake land, we can then generate Android archives using a CPack generator (script).

Describe alternatives you've considered

Manually copy and and generate prefab json files.

Additional context

@madebr madebr added the enhancement New feature or request label Sep 5, 2024
@DanAlbert
Copy link
Member

DanAlbert commented Sep 5, 2024

Huh. I did a whole bunch of research before creating my own but this never came up. I'll have to read more to know for sure, but it looks more like this is an alternative to prefab, so rather than prefab adding support for this, the thing that'd be needed would be for AGP to learn how to consume them. If that's the case I'll raise it with the AGP folks, but I'm not sure at first glance.

I also need to read more closely to see if it's even possible describe the constraints that are important to Android. Conan, for example, could only do exact configuration matching, so the common case of a dependency built for a lower API level than your app would be "incompatible", despite being perfectly usable.

This would be a pretty good solution for solving the "this is a huge pain outside AGP" problem we currently have native AARs if it works. Thanks for the pointer!

Unfortunately, don't expect anything about this to change quickly. As you can probably tell from me being the person that responds on several different projects, we're spread pretty thin.

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

No branches or pull requests

2 participants