Re: prerelease 4

On 2 Mar 2003, James K. Lowden wrote:
What better to do on a rainy Sunday than dig into arcane font stuff, eh?


Your explanation was very helpful.  

It turns out the message is misleading: config.log showed that freetype.h
was not found.  It was not found because `freetype-config --cflags` lied.
It's a shell script, and apparently (I haven't confirmed this yet) the
NetBSD freetype2 package is slightly looney.  For sure, `freetype-config
--cflags` was returning a bogus path.  I edited the script to return
something reasonable, but I wonder what I really should fix.  What does
your directory show for something like:

$ pkg_info -L freetype2 |grep -E 'ft2|freetype.h'

$ dpkg -L libfreetype6-dev | grep -E 'ft2|freetype.h' | grep -v doc

configure wants those two files in the same directory.  Is that your
setup, too?  Mine obviously are not.  And before you ask,  :-) these are
the right files:

$ find /usr/pkg/include/ -name freetype\*.h |xargs grep 'FREETYPE_M.*R'
|grep define
/usr/pkg/include//freetype2/freetype/freetype.h:#define FREETYPE_MAJOR 2
/usr/pkg/include//freetype2/freetype/freetype.h:#define FREETYPE_MINOR 1
/usr/pkg/include//freetype/freetype.h:#define TT_FREETYPE_MAJOR  1
/usr/pkg/include//freetype/freetype.h:#define TT_FREETYPE_MINOR  3

$ dpkg -L libfreetype6-dev | grep -E 'ft2|freetype.h' | grep -v doc | xargs grep 'FREETYPE_M.*R'
/usr/include/freetype2/freetype/freetype.h:  /* The FREETYPE_MAJOR and FREETYPE_MINOR macros are used to 
version the  */
/usr/include/freetype2/freetype/freetype.h:#define FREETYPE_MAJOR 2
/usr/include/freetype2/freetype/freetype.h:#define FREETYPE_MINOR 1
/usr/include/freetype2/freetype/freetype.h:  /*    use the macros FT_FREETYPE_MAJOR, FT_FREETYPE_MINOR, and   

You have a version of FreeType 1 installed, maybe that is causing confusion?

I can patch the NetBSD freetype2 package (I think), but before I do, what
should the target directory structure be?  Do you normally rely on the

Your directory structure looks ok, just in an unusual place.  FT2 uses a
strange macro for its include, instead of having freetype-config point to it.

I realize we've wandered afield here; the problems I'm encountering have
nothing to do with Dia per se.  I guess the only benefit to Dia would be
potentially a more granular freetype2 test.  

It is indeed outside our normal scope, but if it helps you set up Dia...
We can't really do much to do a better test except alert BSD and/or
FreeType2 people to the problem.


Lars Clausen (| HÃrdgrim of Numenor
"I do not agree with a word that you say, but I   |----------------------------
will defend to the death your right to say it."   | Where are we going, and
    --Evelyn Beatrice Hall paraphrasing Voltaire  | what's with the handbasket?

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]