Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Solving the mesa3d build issue
Date: Thu, 22 Nov 2012 08:34:27 +0100	[thread overview]
Message-ID: <20121122083427.0c93fa51@skate> (raw)
In-Reply-To: <50AD1EC3.4090401@mind.be>

Arnout,

On Wed, 21 Nov 2012 19:34:43 +0100, Arnout Vandecappelle wrote:

>   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?

This is indeed another solution. But just like the kconfig knob for a
host package creates a precedent, having two separate binary packages
for one single source package is also creating another precedent. I'm
not sure which is not is better, really.

Or maybe it's time for Buildroot to make the distinction between source
packages and binary packages? But this is going to be a very large
change.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2012-11-22  7: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
2012-11-22  7:34   ` Thomas Petazzoni [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=20121122083427.0c93fa51@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