From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Cc: Daniel Lang <dalang@gmx.at>, Bernd Kuhls <bernd@kuhls.net>,
Simon Dawson <spdawson@gmail.com>,
James Knight <james.knight@collins.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/at-spi2-core: propagate dynamic library dependency
Date: Mon, 15 Jul 2024 20:49:08 +0200 [thread overview]
Message-ID: <20240715204908.570651f2@windsurf> (raw)
In-Reply-To: <bac58c99-45bc-4d7d-9b34-1fca6bbdfd24@mind.be>
On Fri, 12 Jul 2024 22:08:09 +0200
Arnout Vandecappelle via buildroot <buildroot@buildroot.org> wrote:
> We're months later, the bump to 2.50.0 has been merged, so it should be
> possible now to drop the dependency on !STATIC, right? IIUC it takes a little
> more effort because we also need a way to enable/disable the gtk2_atk_adaptor
> option...
Thing is that I don't see how the gtk2_atk_adaptor option pointed by
Daniel Lang can help, and how it relates to dlopen() being needed or
not.
Indeed, in meson.build, regardless of gtk2_atk_adaptor, I see:
if not get_option('atk_only')
if cc.has_function('dlopen')
dl_dep = []
elif cc.has_function('dlopen', args: '-ldl')
dl_dep = cc.find_library('dl')
else
error('Could not find a library with the dlopen function')
endif
endif
so unless atk_only is defined, dlopen() will be needed. atk_only is
defined as such:
option('atk_only',
description: 'Build only the ATK stub library without atspi or at-spi2-atk (UNSUPPORTED)',
type: 'boolean',
value: false)
of course the UNSUPPORTED is a bit scary. But perhaps that would make
sense in the context of Buildroot. Both libgtk2/libgtk3 require
at-spi2-core, but we can imagine that real accessibility support is not
always needed, so being able to build a stub at-spi2-core might be
interesting, and that would allow to not require dlopen(), apparently.
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
next prev parent reply other threads:[~2024-07-15 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 15:49 [Buildroot] [PATCH 1/1] package/at-spi2-core: propagate dynamic library dependency Fabrice Fontaine
2023-09-19 4:42 ` Daniel Lang
2023-09-19 6:22 ` Fabrice Fontaine
2023-09-20 3:51 ` Daniel Lang
2024-07-12 20:08 ` Arnout Vandecappelle via buildroot
2024-07-15 18:49 ` Thomas Petazzoni via buildroot [this message]
2024-07-15 19:12 ` 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=20240715204908.570651f2@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=dalang@gmx.at \
--cc=fontaine.fabrice@gmail.com \
--cc=james.knight@collins.com \
--cc=spdawson@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