From: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>, buildroot@buildroot.org
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] GLib/GObject-introspection bootstrap
Date: Tue, 20 Aug 2024 00:16:49 +0200 [thread overview]
Message-ID: <1a14c38e-2d3e-4a63-8f03-9bd6cc1861ff@bubu1.eu> (raw)
In-Reply-To: <44f9f8a3-9ebf-4cad-acd8-1b6331581c72@gmx.de>
Hi Fiona,
I looked into this a few weeks back as well (but am unlikely to find
time to continue working on this in the near future).
The conclusion we came to on IRC was, that introducing a
libglib2-initial package similar to gcc-initial would be the best/only
option. (Which gets added as a dependency to gobject-introspection which
then gets used to build the final libglib2.)
I didn't actually get to trying this out, so no guarantees :).
Best,
Marcus
On 19.08.24 19:52, Fiona Klute via buildroot wrote:
> Hi everyone,
>
> I'm currently trying to upgrade GLib & GObject-introspection to their
> current versions (1.80.4 and 1.80.1), not least because those work with
> musl without patching. The difficulty is that GLib now needs a sort of
> bootstrap process:
>
> * Build GLib with -Dintrospection=disabled
> * Build GObject-introspection
> * Build GLib with -Dintrospection=enabled
>
> Description in the GLib NEWS file:
> https://gitlab.gnome.org/GNOME/glib/-/
> blob/17d1bf3c4962d942feea0830aeee6833104fef5d/NEWS#L429-438
>
> What would be the preferred way to implement this in Buildroot? Is there
> a built-in way to rebuild a package with different config after building
> another package for such situations? Or should I include that bootstrap
> build of GObject-introspection in libglib2.mk (like Alpine does)? In the
> latter case the GLib package would share the source archive with
> GObject-introspection and I remember reading on the ML that there's
> support for that, would be great if someone could point me at it if
> relevant.
>
> Also, when I prepare patches, should I just drop the glibc requirement
> for GObject-introspection, or add musl? I have no idea if it works with
> uClibc. Likewise, are the checks for (ancient) GCC versions still relevant?
>
> Best regards,
> Fiona
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-19 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 17:52 [Buildroot] GLib/GObject-introspection bootstrap Fiona Klute via buildroot
2024-08-19 20:30 ` Yann E. MORIN
2024-08-21 13:38 ` Fiona Klute via buildroot
2024-08-19 22:16 ` Marcus Hoffmann via buildroot [this message]
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=1a14c38e-2d3e-4a63-8f03-9bd6cc1861ff@bubu1.eu \
--to=buildroot@buildroot.org \
--cc=buildroot@bubu1.eu \
--cc=fiona.klute@gmx.de \
--cc=fontaine.fabrice@gmail.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 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.