Freetype libs in /usr/include/libs

[Gerald Pfeifer]

A user notified me that even if his system has Freetype2 installed,
Wine fails to detect that during configure, for he has installed it
in /usr/local instead of /usr/X11R6.

The patch below fixes this, but I'm not sure whether it's the right
approach.

If it is not, how shall we handle this, assuming /usr/local is a
standard prefix which I think we should always consider?

Gerald

Index: configure.ac
===================================================================
RCS file: /home/wine/wine/configure.ac,v
retrieving revision 1.165
diff -u -3 -p -r1.165 configure.ac
--- configure.ac	1 Jul 2003 01:11:13 -0000	1.165
+++ configure.ac	7 Jul 2003 08:44:30 -0000
@@ -429,7 +429,7 @@ then
 fi

 dnl **** Check for FreeType 2 ****
-AC_CHECK_LIB(freetype,FT_Init_FreeType,ft_lib=yes,ft_lib=no,$X_LIBS)
+AC_CHECK_LIB(freetype,FT_Init_FreeType,ft_lib=yes,ft_lib=no,-L/usr/local/lib $X_LIBS)
 if test "$ft_lib" = "no"
 then
     FREETYPEINCL=""

[Lionel Ulmer]

> If it is not, how shall we handle this, assuming /usr/local is a
> standard prefix which I think we should always consider?

Well, if the user is advanced enough to install packages in non-standard
locations, he should also know about the LDFLAGS option for configure :

  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
              nonstandard directory <lib dir>

So I would say that this is an user bug, not a Wine bug.

       Lionel

-- 
		 Lionel Ulmer - http://www.bbrox.org/

[Jeff Smith]

If I am not mistaken, /usr/local/lib is the *standard* location to find
the freetype libraries, if it is built stand-alone, as opposed to being
built as part of XFree86.  Of course, I would have thought that
/usr/local/lib should be a part of the standard library search path.

Note that we should probably first try pkg-config, then freetype-config,
then fall back on standard locations when looking for the freetype
libraries.

 -- Jeff Smith


--- Lionel Ulmer <lionel.ulmer(a)free.fr> wrote:
> > If it is not, how shall we handle this, assuming /usr/local is a
> > standard prefix which I think we should always consider?
>
> Well, if the user is advanced enough to install packages in non-standard
> locations, he should also know about the LDFLAGS option for configure :
>
> LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
>               nonstandard directory <lib dir>
>
> So I would say that this is an user bug, not a Wine bug.
>
> Lionel

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Marcus Meissner]

On Mon, Jul 07, 2003 at 12:34:31PM -0700, Jeff Smith wrote:
> If I am not mistaken, /usr/local/lib is the *standard* location to find
> the freetype libraries, if it is built stand-alone, as opposed to being
> built as part of XFree86.  Of course, I would have thought that
> /usr/local/lib should be a part of the standard library search path.
>
> Note that we should probably first try pkg-config, then freetype-config,
> then fall back on standard locations when looking for the freetype
> libraries.

And we do not even link against them, we just need the headers.

The libraries are loaded dynamically, where the search path is not honored
yet.

Ciao, Marcus