From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Solving the mesa3d build issue
Date: Wed, 21 Nov 2012 19:34:43 +0100 [thread overview]
Message-ID: <50AD1EC3.4090401@mind.be> (raw)
In-Reply-To: <20121117150357.2aa86a1c@skate>
On 17/11/12 15:03, Thomas Petazzoni wrote:
> Hello,
>
> The mesa3d build is currently broken because it generates during its
> build process a bunch of C files from a XML description of the OpenGL
> APIs. This generation process is done through Python scripts that
> require the libxml2 Python bindings to be installed.
>
> Unfortunately, those libxml2 Python bindings are part of the libxml2
> source code itself, so we would have to enable host-python as a
> dependency of host-libxml2 in order to get those Python bindings built
> and installed. This means that all other users of host-libxml2 would
> pay the price of building host-python even if they don't need it, which
> is quite annoying.
>
> We have several solutions to address this problem:
>
> (1) The solution proposed by Will Wagner/Noel Vellemans at
> http://lists.busybox.net/pipermail/buildroot/2012-November/061594.html
> and
> http://lists.busybox.net/pipermail/buildroot/2012-November/061595.html.
>
> This solution consists in adding a BR2_PACKAGE_HOST_LIBXML2_PYTHON
> hidden configuration symbol, that mesa3d selects. It sells the
> host-libxml2 package that it should build the Python binding, and
> therefore depend on host-python.
>
> It is quite nice in the sense that it is simple and only builds
> host-python as a dependency of host-libxml2 when needed. However,
> it adds something entirely non-standard: a hidden kconfig option
> that tunes the compilation of a host package. Do we want to do
> this?
>
[snip (2) and (3)]
A fourth solution would be to create a new host-only package libxml2-python
that builds libxml2 with python bindings. It would just reuse the libxml2
package with a slightly different CONF_OPT.
The differences with the currently committed solution (1) are:
- No need for a HOST-config symbol.
- host-libxml2 will be built twice, once without and once with python bindings.
There may even be a workaround for the second step, but at the moment I assume
it will be built twice.
What do you think?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-11-21 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 14:03 [Buildroot] Solving the mesa3d build issue Thomas Petazzoni
2012-11-17 16:49 ` Peter Korsgaard
2012-11-21 18:34 ` Arnout Vandecappelle [this message]
2012-11-22 7:34 ` Thomas Petazzoni
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=50AD1EC3.4090401@mind.be \
--to=arnout@mind.be \
--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 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.