Re: [gtk-osx-users] getting rid of the /usr/X11/lib/libfreetype.6.dylib dependency

[Antoine Martin <antoine nagafix co uk>]

On 09/07/13 03:51, John Ralls wrote:
> On Jul 8, 2013, at 9:05 AM, Antoine Martin <antoine nagafix co uk> wrote:
>
> > On 08/07/13 21:33, John Ralls wrote:
> > > On Jul 8, 2013, at 1:58 AM, Antoine Martin <antoine nagafix co uk> wrote:
> > >
> > > > Hi,
> > > >
> > > > I've found some previous posts on the subject:
> > > > https://mail.gnome.org/archives/gtk-osx-users-list/2013-April/msg00002.html
> > > >
> > > > But I still cannot get my dylibs to be X11 free:
> > > >
> > > > $ for x in `ls *dylib`; do otool -L $x | grep -i X11 && echo $x; done
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgailutil.18.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgailutil.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgdk-quartz-2.0.0.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgdk-quartz-2.0.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgdkglext-quartz-1.0.0.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgdkglext-quartz-1.0.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgtk-quartz-2.0.0.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgtk-quartz-2.0.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgtkglext-quartz-1.0.0.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgtkglext-quartz-1.0.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgtkmacintegration.2.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libgtkmacintegration.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libpangocairo-1.0.0.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > libpangocairo-1.0.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > librsvg-2.2.dylib
> > > >         /usr/X11/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0)
> > > > librsvg-2.dylib
> > > >
> > > > What am I missing?
> > > > It doesn't seem to have any adverse effects, but I would still like to get rid of it if I can.
> > > Did you try the solution Miroslav proposed in his email?
> > Yes, I had.
> > > If that doesn't work, look at libpangocairo and see if it's pulling in something from outside your prefix
> > > that might be dragging in libfreetype.
> > Rebuilding freetype:
> > jhbuild build -f freetype
> > Then rebuilding all the affected packages seems to be doing the trick.
> >
> > Sorry for the noise.
> That just moves the freetype dependency inside your build,
You're right.
I thought that was the case, but I wasn't sure whether the dependency
was actually required for anything, thanks for clarifying that.

Moot point:  I figured it was still cleaner than depending on the system
one.
For one, because I can pay attention to the build warnings again.
>  but freetype by itself doesn't do you much good: You also need fontconfig and harfbuzz. You can build all 
> three with meta-gtk-osx-freetype.
>
> But unless you have a package which is using the low-level pangoft2 API, you don't really want freetype at 
> all. I suggest you dig into it a bit more and figure out what's pulling it in and why.
I think what must have happened is that I ended up with a pkg-config
file for freetype, and the build for various bits (cairo, pango?) seem
to pick that up, adding "-lfreetype" to the build..
Removing freetype and clearing any reference to it then rebuilding
everything gives me clean, X11-free dylibs again.

Thanks
Antoine


> Regards,
> John Ralls