Re: [AD] Request: adding textout_ex(), which takes bg color as parameter

[Peter Wang <tjaden@xxxxxxxxxx>]

On 2002-10-01, Eric <ebotcazou@xxxxxxxxxx> wrote:
> > --- src/fsel.c 1 Oct 2002 17:31:46 -0000 1.29
> > +++ src/fsel.c 1 Oct 2002 18:33:06 -0000
> > @@ -31,6 +31,7 @@
> >
> >
> >  #include "allegro.h"
> > +#include "allegro/alcompat.h"
> >  #include "allegro/internal/aintern.h"
> 
> I don't know. According to these lines in allegro.h:
> 
> #ifndef ALLEGRO_LIB_BUILD
>    #include "allegro/alcompat.h"
> #endif
> 
> it seems it is not safe to include alcompat.h while building the library on
> Unix.

I think Grzegorz's patch is fine.  Below is a message leading to
ALLEGRO_LIB_BUILD.  IIRC it was originally ALLEGRO_NO_FIX_ALIASES to avoid
clashes with math.h on IRIX, then it got generalised.


On 2002-01-18, Stepan Roh <stepan@xxxxxxxxxx> wrote:
> User programs will compile as long as they don't include math.h. Library
> must be built with ALLEGRO_NO_FIX_ALIASES because there are few files
> using math.h and same applies to examples (e.g. exshade.c), tests (e.g.
> test.c) and tools (pat2dat.c). Library and shipped tools should not use
> any features from alcompat.h, so it is safe to disable it, but user
> programs should be allowed to use those features as long as they are not
> using old-style f*() functions.

-- 
王浩禎