| Re: [AD] loadable modules |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Tue, 2008-10-07 at 18:37 +0200, Milan Mimica wrote:
> Some addons have external dependencies which must be satisfied when running an
> app linked to these addons, in case of shared build, and when linking an app, in
> case of static link.
> The result is that you must ship FLAC.dll even if your game is never going to
> load any FLACs. On Linux the situation is even worst, kcm_audio may want ALSA
> while it is not available on the system...
>
> Can you think of a simple way to fix this? Loadable modules in A4 where quite
> complicated, as far I've looked into them.
> On Windows at least, I think this is quite simple. Just LoadLibrary() and
> GetProcAddress().
>
> Anyone knows what made it complicated on linux? Why did we need modules?
>
Loadable modulesin A4 were rather simple. Our alsa module is just
another .so file which is linked against alsa. Allegro then on startup
tries to load it. That's it. What was complicated was the way to locate
our module .so files, and all the build options to support building
without modules.
--
Elias Pschernig <elias@xxxxxxxxxx>