All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Antw: build speedup possible?
Date: Mon, 10 Feb 2014 13:15:56 +0100	[thread overview]
Message-ID: <20140210131556.4498d0d0@skate> (raw)
In-Reply-To: <52F8B87C.4070201@andin.de>

Dear Andreas Naumann,

On Mon, 10 Feb 2014 12:31:08 +0100, Andreas Naumann wrote:

> > If we want to get this to the next level, someone need to experiment
> > with per-package sysroot. Of course, this would be a long experiment,
> > without necessarily at the end the guarantee that we will accept it,
> > because it may be too complex to match Buildroot simplicity principle.
> 
> as I said, we have hacked br to a per-package sysroot in the past. This 
> was in order to create isolated ipkgs and did its job. Even if we dont 
> solve any of the dependency issues with that, it could be a starting 
> point. If this is of  interest I can try to go further with it.

Investigation in this area are definitely welcome. But as I said, we
cannot guarantee that it will be merged: it will highly depends on how
much additional complexity it will add.

> And for the depency issue, how does OE solve it?

I don't know exactly. The author of oe-lite (http://oe-lite.org/) told
me that they don't do per-package sysroot (which in his opinion is
fundamentally wrong when you do parallel build of multiple packages),
and it indeed seems to be the case from a quick look at what Yocto is
doing. That being said, my knowledge of OE/Yocto internals is almost
non-existent, so I don't know how they solve this problem.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2014-02-10 12:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07  8:51 [Buildroot] build speedup possible? Andreas Naumann
2014-02-07  8:54 ` Maxime Hadjinlian
2014-02-07  9:00 ` [Buildroot] Antw: " Frank Ihle
2014-02-07 10:31   ` Samuel Martin
2014-02-07 13:35     ` Andreas Naumann
2014-02-07 15:17       ` Fabio Porcedda
2014-02-07 14:48     ` Fabio Porcedda
2014-02-07 15:03       ` Fabio Porcedda
2014-02-07 15:29       ` Thomas Petazzoni
2014-02-07 15:54         ` Fabio Porcedda
2014-02-07 16:43           ` Thomas Petazzoni
2014-02-07 18:05             ` Fabio Porcedda
2014-02-10  8:38               ` Thomas Petazzoni
2014-02-10 11:31             ` Andreas Naumann
2014-02-10 12:15               ` 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=20140210131556.4498d0d0@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 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.