From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] Remove cairo dependency from gobject-introspection
Date: Wed, 8 Feb 2023 15:23:43 +0100 [thread overview]
Message-ID: <20230208152343.20d46c7d@windsurf> (raw)
Hello James,
Here at the Buildroot Developers Meeting, we ended up looking at where
util-linux-libs gets used, and we found out it's used in fontconfig.
Since util-linux-libs was originally introduced to break a circular
dependency involving systemd and util-linux, we found it strange that
fontconfig was involved in that.
Turns out that there is a possible circular dependency like this:
util-linux -> udev -> systemd -> polkit -> gobject-introspection -> cairo -> fontconfig -> util-linux
What is obviously strange in there is the dependency of
gobject-introspection on cairo, which comes from:
ifeq ($(BR2_PACKAGE_CAIRO),y)
GOBJECT_INTROSPECTION_DEPENDENCIES += cairo
GOBJECT_INTROSPECTION_CONF_OPTS += -Dcairo=enabled
else
GOBJECT_INTROSPECTION_CONF_OPTS += -Dcairo=disabled
endif
However, according to gobject-introspection's meson_options.txt:
option('cairo', type: 'feature', value : 'auto',
description: 'Use cairo for tests'
)
it seems like cairo is only used for tests, which we really don't care
about.
If that's indeed true, do you think you could drop that optional
dependency in gobject-instrospection, pass -Dcairo=disabled
unconditionally, and cleanup fontconfig to not need util-linux-libs
(see commit eb058222596d83bbdc96c80c5d0cdecb572a4ac3) ?
Thanks a lot!
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:[~2023-02-08 14:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230208152343.20d46c7d@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.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