Re: [gtk-osx-users] Bundling, Mountain Lion, and X11 freetype library [SOLVED]
- From: John Ralls <jralls ceridwen us>
- To: Kristaps Dzonsons <kristaps bsd lv>
- Cc: gtk-osx-users-list gnome org
- Subject: Re: [gtk-osx-users] Bundling, Mountain Lion, and X11 freetype library [SOLVED]
- Date: Sun, 9 Mar 2014 13:58:30 -0700
On Mar 9, 2014, at 1:44 PM, Kristaps Dzonsons <kristaps bsd lv> wrote:
John,
Thanks for your response!
In installing a fresh version of the GTK+3 suite with the jhbuild directions, I still had X11 freetype
being pulled into the mix (this is on a Snow Leopard OR Lion machine with /usr/X11 installed).
However, I was able to account for this by preloading some modules before the main GTK+3 build as follows.
The following occurs after running the gtk-osx setup script.
% jhbuild bootstrap
% jhbuild build libpng
% jhbuild build freetype
% jhbuild build meta-gtk-osx-bootstrap
% jhbuild build meta-gtk-osx-gtk3
Running otool -L over all gtk/inst/lib libraries, there was no inclusion of X11. The preloading of libpng
is because freetype would try to link into X11's libpng.
If you build meta-gtk-osx-bootstrap *before* freetype, it will build libpng for you. If you build freetype
instead of meta-gtk-osx-freetype, you get only freetype, no Harfbuzz and no fontconfig. Dunno if that matters
to you. It’s also better to put all of your build modules in a single command. That lets jhbuild figure out
the optimal build sequence based on individual packages’ dependencies.
You can also save yourself some typing by setting the modules list in your .jhbuildrc-custom:
modules = [‘meta-gtk-osx-bootstrap’, ‘meta-gtk-osx-freetype’, ‘meta-gtk-osx-gtk3’, ‘yourapp’]
Then you need only run
jhbuild bootstrap
jhbuild build
Regards,
John Ralls
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]