Re: [ft] freetype build failing when flow-tools is present

[Werner LEMBERG]

> [...] is there a way that we can have FreeType look for its
> ftconfig.h in the build directory anyway and not look to a possibly
> wrong one in the directory given in CPPFLAGS?

Yes.  You can change the `CFLAGS' variable as follows while calling `make':

   CFLAGS="$CFLAGS -UFT_CONFIG_CONFIG_H -DFT_CONFIG_CONFIG_H=..."

> The failing compile line is:
>
> libtool: compile: \
>   /usr/bin/gcc-4.0 \
>   -I/opt/local/include \
>   -I/opt/local/var/.../work/freetype-2.3.9/objs
>   -I./builds/unix \
>   -I/opt/local/var/.../work/freetype-2.3.9/include \
>   -c \
>   -O2 \
>   -DFT_CONFIG_OPTION_SYSTEM_ZLIB \
>   -DDARWIN_NO_CARBON
>   "-DFT_CONFIG_CONFIG_H=<ftconfig.h>" \
>   -DFT2_BUILD_LIBRARY
>   "-DFT_CONFIG_MODULES_H=<ftmodule.h>" \
>   builds/unix/ftsystem.c
>   -fno-common \
>   -DPIC \
>   -o /opt/local/var/.../work/freetype-2.3.9/objs/.libs/ftsystem.o
>
> I see -I/opt/local/include is first, hence that's where ftconfig.h
> is found first.  Perhaps that should be the last -I that's listed,
> instead of the first?

I don't think so.  The idea of `CPPFLAGS' is to override other
preprocessor flags.


    Werner