From: Hadrien Boutteville <hadrien.boutteville@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 6/9] libgtk3: new package
Date: Wed, 16 Jul 2014 14:22:53 +0200 [thread overview]
Message-ID: <53C66E9D.5070507@gmail.com> (raw)
In-Reply-To: <20140708173455.GB25364@rmm-p1267483>
Hi,
On Tue, 8 Jul 2014 19:34:57 +0200, Eric Le Bihan wrote:
>> diff --git a/package/libgtk3/libgtk3-0002-add-file-introspection-m4.patch b/package/libgtk3/libgtk3-0002-add-file-introspection-m4.patch
>> new file mode 100644
>> index 0000000..3cd0569
>> --- /dev/null
> I guess the addition of this file is needed because you have to perform an
> autoreconf, but GOBJECT_INTROSPECTION_CHECK could not be resolved, right?
Yes. It's the solution given by the GTK+3 doc.
> Maybe you can avoid it by patching configure.ac, to add a check, as performed
> in Systemd:
>
> m4_ifdef([GOBJECT_INTROSPECTION_CHECK],
> [GOBJECT_INTROSPECTION_CHECK([1.31.1])],
> [AM_CONDITIONAL([HAVE_INTROSPECTION], [false])
> enable_introspection=no])
I will test, I actually prefer this solution rather than adding a file.
Thanks!
>> +
>> +# We do not build a full version of libgtk3 for the host, because that
>> +# requires compiling Cairo, Pango, ATK and X.org for the
>> +# host. Therefore, we patch it to remove dependencies, and we hack the
>> +# build to only build gdk-pixbuf-from-source and
>> +# gtk-update-icon-cache, which are the host tools needed to build Gtk
>> +# for the target.
I realized that I forget to modify the comment for this part :-/. This
comment was for my first attempt with a patch which reduced dependencies
like for libgtk2. Now we don't patch to reduce dependencies and we just
manually build gtk-update-icon-cache to get rid of the dependencies and
the configure.
>> +HOST_LIBGTK3_DEPENDENCIES = host-libglib2 host-libpng host-gdk-pixbuf
>> +
>> +HOST_LIBGTK3_CFLAGS = $(shell $(HOST_DIR)/usr/bin/pkg-config \
>> + --cflags --libs gdk-pixbuf-2.0)
>
> When experimenting on my side, I've noticed that gtk+ >= 3.10 can build a
> native version of gtk-update-icon-cache if --enable-gtk2-dependency=no is set
> when invoking './configure'.
>
> Unfortunately, if the target toolchain is based on uClibc, the macro
> AM_GLIB_GNU_GETTEXT will detect the libintl built for the target and will add
> '-lintl' to the default list of libraries for the linker (used for both native
> and target builds).
>
> But no native version of libintl is available (the functions are provided by
> glibc): gtk-update-icon-cache will not build...
>
> So, Buildroot must still build its own version, as done in your patch.
Yes, and your solution was better than my first patch ;-).
Thanks,
Hadrien
next prev parent reply other threads:[~2014-07-16 12:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 13:57 [Buildroot] [RFC 0/9] Add libgtk3 and bump webkit to version 2.4.3 Hadrien Boutteville
2014-07-08 13:57 ` [Buildroot] [RFC 1/9] libglib2: bump to version 2.40.0 Hadrien Boutteville
2014-07-08 13:57 ` [Buildroot] [RFC 2/9] pango: bump to version 1.36.3 Hadrien Boutteville
2014-07-08 13:57 ` [Buildroot] [RFC 3/9] cairo: add freetype and gobject support Hadrien Boutteville
2014-07-08 13:57 ` [Buildroot] [RFC 4/9] at-spi2-core: new package Hadrien Boutteville
2014-07-08 13:57 ` [Buildroot] [RFC 5/9] at-spi2-atk: " Hadrien Boutteville
2014-07-08 13:57 ` [Buildroot] [RFC 6/9] libgtk3: " Hadrien Boutteville
2014-07-08 17:34 ` Eric Le Bihan
2014-07-16 12:22 ` Hadrien Boutteville [this message]
2014-07-17 14:09 ` Hadrien Boutteville
2014-07-08 13:57 ` [Buildroot] [RFC 7/9] webkit: bump to version 2.4.3 Hadrien Boutteville
2014-07-08 13:57 ` [Buildroot] [RFC 8/9] libsoup: add libsoup-gnome support Hadrien Boutteville
2014-07-08 13:57 ` [Buildroot] [RFC 9/9] midori: bump to version 0.5.8 Hadrien Boutteville
2014-07-08 16:02 ` Hadrien Boutteville
2014-07-15 21:21 ` [Buildroot] [RFC 0/9] Add libgtk3 and bump webkit to version 2.4.3 Thomas Petazzoni
2014-07-16 12:25 ` Hadrien Boutteville
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53C66E9D.5070507@gmail.com \
--to=hadrien.boutteville@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.