I intend to have a project that is simply an API that I will then use for other projects to build my applications on top of.
I find myself at the very beginning and already not knowing whic is the best practice for continuing (wish me luck on the rest of it).
My idea is a very common one I imagine. The idea of an engine built on top of the Android API which I can therefore reuse in my various upcoming projects.
So my Engine will require access to the Android API this is very clear, I will therefore need to have it somehow in the project but this is my question…
-
Do I make a new Android Project such that it will have its own AndroidManifest.xml etc? This seems like the incorrect way to do things as the Manifest will be of no use. The android projects that will be created for each individual android app will have their own manifests.
-
Or have a project with the Android API as a referenced library? Tgis seems like the propper way to do it but I cannot find any literature on the matter to confirm so.
-
Any other.
Thanks
You create an Android library project. It has a manifest.
With recent additions to the tools, there are ways you can have items in the library’s manifest be automatically added to host projects. That is optional, of course, particularly if there is nothing in the library that would need to be added to host projects.
Correct.
An Android library project will automatically compile against your chosen build target.