Yeah I thought this after I sent the message. You're right. Except you have to build the examples to generate the project, which in my experience is a huge pain except on Linux. But it's probably good enough to move it to the regular system of building examples.

On 04/12/2015 10:06 PM, Elias Pschernig wrote:
On Fri, Dec 4, 2015 at 11:25 PM, Trent Gamblin <[email protected] <mailto:[email protected]>> wrote:

    I think Thomas is right. It's a lot easier to copy that one
    example into your own project than it is to hack out all the CMake
    to create one from the other examples... plus like I said, the
    method most examples use is not sufficient for a real world game.


I think we're talking different things - the only difference would be that instead of copying android/example you would copy build/examples/ex_android.proj - the contents of both folders should be 100% identical. The main benefit besides a less cluttered directory structure (other platform dependent examples are all under examples/ as well) would be that we could de-duplicate some cmake code (android/Example.cmake specifically). Unless you think android/Example.cmake is worth having...


_______________________________________________
Allegro-developers mailing list
[email protected]
https://mail.gna.org/listinfo/allegro-developers

_______________________________________________
Allegro-developers mailing list
[email protected]
https://mail.gna.org/listinfo/allegro-developers

Reply via email to