[Devel] Re: [Freetype] Compiling 2.1.7 on Mac OS X

[Werner LEMBERG]

See below for the various suggestions made to the list(s) how to
improve support for the Mac.  Can someone please try the proposed
solutions (preferably the changes to ftmac.c first) and report the
results?


    Werner


======================================================================


> It looks like configure is setting XX_ANSICFLAGS instead of
> XX_ANSIFLAGS to remove -ansi when this flag is given.  If the inline
> thing isn't fixed, this is an alternative solution.
> 
> > > The error is in the source file ftmac.c, which includes a
> > > Mac-specific header using 'inline' keywords by default.  The
> > > problem comes from the -ansi switch to gcc, as Garrick Meeker
> > > has recently reported, which causes gcc not to recognize
> > > 'inline'.
> > >
> > > The simple solution is to change builds/unix/configure to not
> > > use -ansi if $host matches *-apple*.  However it would be a
> > > shame to disable -ansi for the whole build; do you know how to
> > > tweak the builds/unix makefile so that only ftmac.c is built
> > > without -ansi?  I guess it would have to be separated out from
> > > ftbase.c in that case...
> >
> > Various possibilities come to my mind, to be applied to ftmac.c
> > rather than the makefile:
> >
> >   . Redefine `OS_INLINE' to be `__inline__'.  This survives even
> >     gcc's -ansi switch.
> >
> >   . Redefine `OS_INLINE' to be a no-op.
> >
> >   . Compile FreeType with g++.  `inline' is a normal keyword
> >     then.  [I regularly test whether FreeType really builds with
> >     g++.]