Re: [AD] Android package name

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


On Sun, 17 Nov 2013 12:07:55 +0000, nooskewl@xxxxxxxxxx wrote:
> You can make it not configurable. org.liballeg.android might be a little more fitting.
> 

Ok.

About the startup process:

Instead of setting the application shared library name in
AndroidManifest.xml, we could have the user specify it in the
application Activity class, where all the libraries are listed already.
Something like this:

    class Activity extends AllegroActivity {
        static {
            System.loadLibrary("allegro");
        }
        @Override
        public void onCreate(Bundle savedInstanceState) {
            super.startup(savedInstanceState, "app");
        }
    }

The default implementation of onCreate could default to the library name
"app" or similar.  If you don't mind it then you don't need to override
onCreate at all.  Of course, we could provide a default in the current
system, too.

I think it should be possible to resolve `main' from either a previously
loaded, or the same shared object as Allegro.  Then you could link
everything into one file and write a single Java statement:
System.loadLibrary("app");

Peter




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/