| Re: [AD] GIF patent / support |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Chris:
> I would be all up for including PNG support, and can think of a useable
> way to do it with Windows and Unix with dynamic-loaded libs.. of course
> there'd be a problem with systems that can't use those.
> Basically, I'd just load the .so/DLL manually, import the functions
> manually, and call them as done in loadpng. The zlib and libpng DLLs
> could be distibuted with the Allegro distro (for Windows; Unix could
> just leave it as an optional dependancy.. most would have it anyway) and
> the DLL/.so would be checked when Allegro inits. If the dynamic libs
> don't exist when the program inits, PNG support is disabled but Allegro
> would function normally otherwise. It would be up to the user to require
> libpng/zlib for their individual programs (either by supplying the DLLs
> Allegro has, or as a dependancy).
It would have to also support statically linking against libpng and zlib for
this to be a complete solution. Otherwise, the current situation is better.
I suppose loadpng could be merged into Allegro and #define'd away if
SUPPORT_PNG or some such macro isn't defined. Then ALLEGRO_STATICLINK could
control whether the build system expects to find static or dynamic version
of the libs on the user's system. I don't think the libs should be bundled
unless it is necessary to customize them for use with Allegro, and judging
from loadpng, that's not the case.
--
Daniel Schlyder
http://bitblaze.com/