Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute via buildroot <buildroot@buildroot.org>
Cc: Fiona Klute <fiona.klute@gmx.de>,
	Eric Le Bihan <eric.le.bihan.dev@free.fr>,
	Asaf Kahlon <asafka7@gmail.com>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	James Hilliard <james.hilliard1@gmail.com>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v5 3/7] package/{gobject-introspection, libglib2}: bump to {1.82.0, 2.82.0}
Date: Mon, 28 Oct 2024 22:00:10 +0100	[thread overview]
Message-ID: <20241028220010.23cbd668@windsurf> (raw)
In-Reply-To: <20241010135318.3064224-4-fiona.klute@gmx.de>

Hello Fiona,

On Thu, 10 Oct 2024 15:53:10 +0200
Fiona Klute via buildroot <buildroot@buildroot.org> wrote:

> From: "Fiona Klute (WIWA)" <fiona.klute@gmx.de>
> 
> There are a lot of interconnected changes in these releases:
> 
> Since 2.79.0, the introspection (i11n) data for libglib2 was moved out
> of gobject-introspection (GOI) and into libglib2 itself, thus building
> libglib2 with i11n needs tools provided by GOI [0].

[...]

I finally had a look at this patch, and I have one concern with it: if
I'm not mistaken, host-libglib2 will now always build
host-gobject-introspection, even if we don't care at all about
introspection support.

Why is host-gobject-introspection an unconditional dependency of
HOST_LIBGLIB2_DEPENDENCIES ?

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-10-28 21:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 13:53 [Buildroot] [PATCH v5 0/7] libglib2 2.82 series with bootstrap Fiona Klute via buildroot
2024-10-10 13:53 ` [Buildroot] [PATCH v5 1/7] package/gobject-introspection: don't depend on cairo Fiona Klute via buildroot
2024-10-29 20:35   ` Thomas Petazzoni via buildroot
2024-10-10 13:53 ` [Buildroot] [PATCH v5 2/7] package/gobject-introspection: update homepage Fiona Klute via buildroot
2024-10-29 20:36   ` Thomas Petazzoni via buildroot
2024-10-10 13:53 ` [Buildroot] [PATCH v5 3/7] package/{gobject-introspection, libglib2}: bump to {1.82.0, 2.82.0} Fiona Klute via buildroot
2024-10-28 21:00   ` Thomas Petazzoni via buildroot [this message]
2024-10-29 13:42     ` Fiona Klute via buildroot
2024-11-06 20:45       ` Fiona Klute via buildroot
2024-11-06 21:58         ` Thomas Petazzoni via buildroot
2024-10-10 13:53 ` [Buildroot] [PATCH v5 4/7] package/gobject-introspection: works with musl now Fiona Klute via buildroot
2024-10-10 13:53 ` [Buildroot] [PATCH v5 5/7] package/python-gobject: bump to version 3.50.0 Fiona Klute via buildroot
2024-10-10 13:53 ` [Buildroot] [PATCH v5 6/7] package/network-manager: optional gobject-introspection Fiona Klute via buildroot
2024-10-10 13:53 ` [Buildroot] [PATCH v5 7/7] package/json-glib: bump to version 1.10.0 Fiona Klute 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=20241028220010.23cbd668@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=eric.le.bihan.dev@free.fr \
    --cc=fiona.klute@gmx.de \
    --cc=fontaine.fabrice@gmail.com \
    --cc=james.hilliard1@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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