Re: GNUstep back: won't compile with art support

[Sascha Erni, .rb]

Hi there,

Kazunobu Kuriyama wrote:
> (1) the configure script actually recognizes the freetype library, i.e., 
> it gives you
>    the following messages when it is run:
>      ...
>      checking for main in -lfreetype...yes
>      checking ft2build.h usability...yes
>      checking ft2build.h presence...yes
>      checking for ft2build.h...yes
>      ...
>    In case you get one or more no's, read config.log to see what was the 
> reasons, which
>    may give you a hint how to fix it.

All are ok, i.e. "yes".

> (2) you have freetype2/freetype/cache/ftcimage.h and the compiler knows it.
>    The symbol 'font' that your compiler complained of comes from the 
> header.

Yup, all in place.

> (3) the library has the symbols having the prefix FTC_.  If not, the 
> library wasn't built
>    having the cache subsystem and thus won't work with -art even if -art 
> compiles
>    successfully (If the library comes with X11, this is likely to 
> happen).  If this is
>    the case, you might need to recompile it so that it will have the 
> FTC_ symbols.

Ui. How to check for that?

red,
I will give a self-compile a shot. Here's hoping. Ironic thing is, up to 
yesterday night, I didn't mind lack of art support for GNUstep. Reason: 
Window Maker didn't have anti-aliased fonts, hence I liked the "common" 
look of xlib for back and Window Maker (both with no AA, that is). Now, 
having installed 0.90.0 with AA for Window Maker (cvs), non-anti-aliased 
GNUstep applications stick out like a Mickey Mouse tie at a funeral.

Kind regards,
-Sascha.rb

--
Sascha "nggalai" Erni, .rb
www.dudagroup.com
www.3dcenter.de
www.nggalai.com