nanogui: freetype 2.2.1
Subject:
Re: [nanogui] freetype 2.2.1
From:
Reza Roboubi ####@####.####
Date:
11 May 2007 00:52:21 +0100
Message-Id: <4643AFB4.5090109@parvan.net>
Greg Haerr wrote:
> : I'm having trouble compiling with the freetype2 installed on my Ubuntu
> : edgy box. Not sure what version, but nano-x detects it as freetype 2.2.1.
>
> The Freetype 2 implementation requires a certain version or later of
> Freetype. See src/engine/font_freetype2.c for details. IIRC it
> was tested with v2.1.3, and there are some fancy #defines for
> checking for later versions. Without seeing your errors I'm only
> guessing that there some structure member name changes.
Yes, you're absolutely right. The error is:
/home/reza/tmp/downloads/microwindows-0.91/src/engine/font_freetype2.c:
In function ‘freetype2_createfont_internal’:
/home/reza/tmp/downloads/microwindows-0.91/src/engine/font_freetype2.c:618:
error: ‘FTC_ImageTypeRec’ has no member named ‘font’
>
>
> :
> : Also, a more basic question about X: What _are_ fonts for anyway?
> : Don't "fltk" or other apps just use the font library directly, then
> : render the resulting image onto an X display? Does X _need_ fonts?
>
> Fonts are for quickly drawing bitmaps which humans are
> accustomed to seeing as language glyphs.
>
> FLTK, when running under X11, uses the X11 font library
> directly, which NXLIB handles the conversion to nano-X.
> When running FLNX, the font code was rewritten for
> direct nano-X use.
>
> X doesn't need fonts, but usually has a builtin font so it
> can at least display something when a text output API
> is called (nano-X is the same way).
Thanks Greg. I read the code and found out that this is what's going
on. I appreciate your response.
Reza.
>
> Regards,
>
> Greg
>
>
