| Re: [AD] statically linking small addons |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: "Coordination of admins/developers of the game programming library Allegro" <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] statically linking small addons
- From: Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx>
- Date: Mon, 10 Aug 2009 21:04:34 -0600
On Mon August 10 2009, Elias Pschernig wrote:
> On Mon, 2009-08-10 at 10:45 -0600, Trent Gamblin wrote:
> > > Secondly, ALLEGRO_STATICLINK. I'm fuzzy on what it does exactly so
> > > would someone explain if there will be any trouble with that?
> >
> > I'm not sure it's necessary anymore. I've been linking statically for a
> > while and I'm not using it.
>
> So can we get rid of all the ugly preprocessor magic like for example:
>
> #if (defined ALLEGRO_MINGW32) || (defined ALLEGRO_MSVC) || (defined
> ALLEGRO_BCC32) #ifndef ALLEGRO_STATICLINK
> #ifdef A5_TTF_SRC
> #define _A5_TTF_DLL __declspec(dllexport)
> #else
> #define _A5_TTF_DLL __declspec(dllimport)
> #endif
> #else
> #define _A5_TTF_DLL
> #endif
> #endif
>
> Last time I was wondering about it someone explained that this will
> always be needed, as the functions are actually named differently if
> they are in th DLL.
That might have changed with the change to named symbols in the dlls. Though
I'm not sure.
--
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx