I think it’s just because it used to be the only example, and we didn’t have CMake able to build for Android.
IMO it is still useful because you get to see the structure of an Android project. The CMake that builds the examples is simplified, at least I know for my projects I use a special build for Android with a directory like that example. It’s good to know the directory structure so you can use it or set up your own CMake script to build your Android project. Like for example, the examples use a generic AndroidManifest.xml whereas you often need to add things that the tools can’t do via command line. And many other things. If possible I think it’d be better to keep it and set the correct architectures and stuff, or at least put it in misc/ and allow users to build it manually if they want to try it out or something. From: Allegro-developers [mailto:[email protected]] On Behalf Of Elias Pschernig Sent: December 4, 2015 3:37 PM To: [email protected] Subject: [AD] android example Is there a reason the android example lives in android/example and not in examples/ like all the other examples? The reason I ask is because the cmake for that example is rather bad... it hardcodes some stuff like the used architecture and writes generated files into the source folder and so on. I believe originally the examples in the examples folder did not compile under Android at all so this one example was better than nothing. But now that all examples build under Android (and in a much better way, using all the cmake variables and writing generated files into the build folder) I'd like to do something like: mv android/example examples/ex_android But maybe this example does something special or is used as a template or something, so thought I better ask first.
_______________________________________________ Allegro-developers mailing list [email protected] https://mail.gna.org/listinfo/allegro-developers
