Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Adrian Perez de Castro <aperez@igalia.com>,
	Thomas Devoogdt <thomas.devoogdt@barco.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1] package/libgtk4: fix cairo-pdf compile error
Date: Tue, 3 Sep 2024 23:14:53 +0200	[thread overview]
Message-ID: <20240903231453.2fc15914@windsurf> (raw)
In-Reply-To: <20240829131232.2132854-3-thomas@devoogdt.com>

On Thu, 29 Aug 2024 15:12:30 +0200
Thomas Devoogdt <thomas@devoogdt.com> wrote:

> From: Thomas Devoogdt <thomas.devoogdt@barco.com>
> 
> ../gtk/print/gtkprintoperation.c:26:10: fatal error: cairo-pdf.h: No such file or directory
> 
> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
> ---
>  package/libgtk4/Config.in | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/package/libgtk4/Config.in b/package/libgtk4/Config.in
> index af7f57b80e..2fcae311d7 100644
> --- a/package/libgtk4/Config.in
> +++ b/package/libgtk4/Config.in
> @@ -23,6 +23,7 @@ config BR2_PACKAGE_LIBGTK4
>  	# https://gitlab.gnome.org/GNOME/gtk/-/issues/6866.
>  	depends on BR2_PACKAGE_HAS_LIBEGL
>  	select BR2_PACKAGE_CAIRO
> +	select BR2_PACKAGE_CAIRO_ZLIB

We had a previous patch somewhat similar to this (but not exactly), and
I made this reply:

https://lore.kernel.org/buildroot/20240815000358.6887f1bf@windsurf/

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-09-03 21:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 13:12 [Buildroot] [PATCH v1] package/libsoup3: bump to 3.6.0 Thomas Devoogdt
2024-08-29 13:12 ` [Buildroot] [PATCH v1] package/midori: drop package Thomas Devoogdt
2024-09-01 12:11   ` [Buildroot] [PATCH v1] package/webkitgtk: restore libsoup support Thomas Devoogdt
2024-09-02 15:41     ` Yann E. MORIN
2024-09-02 16:06       ` Thomas Devoogdt
2024-09-02 16:26         ` Yann E. MORIN
2024-09-02 19:37           ` Adrian Perez de Castro
2024-09-02 20:04             ` Yann E. MORIN
2024-09-03 10:54               ` Adrian Perez de Castro
2024-09-02 15:39   ` [Buildroot] [PATCH v1] package/midori: drop package Yann E. MORIN
2024-08-29 13:12 ` [Buildroot] [PATCH v1] package/libgtk4: fix cairo-pdf compile error Thomas Devoogdt
2024-09-03 21:14   ` Thomas Petazzoni via buildroot [this message]
2024-09-03 21:26     ` Thomas Devoogdt
2024-09-14 19:58       ` Thomas Devoogdt
2024-09-17 19:18   ` [Buildroot] [PATCH v2] package/libgtk4: fix compile error if cairo zlib is not enabled Thomas Devoogdt
2024-08-29 13:12 ` [Buildroot] [PATCH v1] package/webkitgtk: start using GTK4 Thomas Devoogdt
2024-09-01 14:15 ` [Buildroot] [PATCH v1] package/libsoup3: bump to 3.6.0 Adrian Perez de Castro
2024-09-05 20:56 ` Thomas Petazzoni via buildroot

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=20240903231453.2fc15914@windsurf \
    --to=buildroot@buildroot.org \
    --cc=aperez@igalia.com \
    --cc=thomas.devoogdt@barco.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=thomas@devoogdt.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox