| Re: [AD] get rid of ALLEGRO_MINGW32 and so on? |
[ 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] get rid of ALLEGRO_MINGW32 and so on?
- From: Peter Wang <novalazy@xxxxxxxxxx>
- Date: Tue, 1 Jun 2010 17:31:02 +1000
On 2010-06-01, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
> On May 31, 2010, Peter Wang wrote:
> >
> > Not sure what you mean, they are all defined in alplatf.h right now.
> > In some (all?) cases they could be defined like:
> >
> > #ifdef __MINGW32__
> > #define ALLEGRO_MINGW32
> > #endif
> >
> > It would be nice to separate out the public and private headers.
> > The public headers should be invariant across installations.
>
> That is pretty much what I meant. Instead of bothering with a bunch of
> separate generated headers, we can just use one hard coded header with a
> bunch of ifdefs.
There's really only one generated header, alplatf.h. Most of this you
can't or don't want to hard code.
The addons have one generated header each, mainly to tell them which
backends to enable. You can't hard code those either.
Peter