[no subject]

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


You could almost get the best of both worlds if there is an optional
include file like:

~~~~
#ifdef ALLEGRO_CFG_IIO_HAVE_PNG
#include "allegro5/allegro_png.h"
#endif

#ifdef ALLEGRO_CFG_IIO_HAVE_JPG
#include "allegro5/allegro_jpg.h"
#endif

#define al_register_all_images() ...
 // al_init_jpeg_addon()
 // al_init_png_addon()
~~~~

Then you could do something like:

#include <allegro5/image.h>

al_register_all_images();

The behavior would be the same as the current one (dependent on all
external libs). However, if you explicitly chose to include just PNG,
you could do so.

The difference would be an extra allegro_jpeg or allegro_png library.

I don't really know which is ultimately better when taking all the
platforms into consideration.


--
Matthew Leverton




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