From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] select and depends on for libraries
Date: Tue, 27 Mar 2012 00:28:21 +0200 [thread overview]
Message-ID: <20120327002821.5b701e8e@skate> (raw)
Hello,
We typically use "select" to mark at the Kconfig level the dependencies
between a package and its libraries. However, when such a dependency
has some "depends on" dependencies, they must be replicated at the
level of all packages that are selecting this dependency, i.e:
config FOO
bool
config PACKAGE_A
depends on FOO
config PACKAGE_B
select PACKAGE_A
depends on FOO # we must have this dependency
I now have the case of libffi. libffi cannot be built for various
architectures, for example Blackfin (see
http://autobuild.buildroot.org/results/3db2d6c1e77b2c6460bd8187588a3590a4329aaf/build-end.log).
libffi being inherently architecture-specific, adding support for new
architectures is not a two-lines fix. So, BR2_PACKAGE_LIBFFI should
"depends on !BR2_bfin".
Unfortunately, libglib2 depends on libffi. So libglib2 would also have
to carry the "depends on !BR2_bfin". And also the ~30 packages that
"select BR2_PACKAGE_LIBGLIB2". And the absolutely enormous number of
packages that "select BR2_PACKAGE_LIBGLIB2", either directly or
indirectly.
Do we really want to do this?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2012-03-26 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 22:28 Thomas Petazzoni [this message]
2012-03-28 21:01 ` [Buildroot] select and depends on for libraries Arnout Vandecappelle
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=20120327002821.5b701e8e@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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