All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	Discussion of the angstrom distribution development
	<angstrom-distro-devel@linuxtogo.org>,
	Ulf Samuelsson <angstrom-dev@emagii.com>
Subject: Re: Improving Build Speed
Date: Thu, 21 Nov 2013 01:10:30 +0100	[thread overview]
Message-ID: <20131121001030.GV3708@jama> (raw)
In-Reply-To: <1384982956.16887.94.camel@ted>

[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]

On Wed, Nov 20, 2013 at 09:29:16PM +0000, Richard Purdie wrote:
> Hi Ulf,
> 
> > (3) Creating the rootfs seems to have zero parallelism.
> >      But I have not investigated if anything can be done.
> 
> This is something I do want to fix in 1.6. We need to convert the core
> to python to gain access to easier threading mechanisms though.
> Certainly parallel image type generation and compression would be a win
> here.

If you're building .bz2 images, then installing lbzip2/pbzip2 saves a
lot of time in FSTYPES creation.

> > DEPENDENCY BUGS
> > pangomm    needs to depend on "pango"
> >      Otherwise, the required pangocairo might not be available when 
> > pangomm is configured
> > 
> > goffice needs to depend on "librsvg gdk-pixbuf"
> >      Also on "gobject-2.0 gmodule-2.0 gio-2.0", but I  did not find 
> > those packages,
> >      so I assume they are generated somewhere. Did not investigate further.
> 
> I'm sure patches would be most welcome for bugs like this.

But please upgrade to latest layers first, because there 2 weren't
detected in my last test-dependencies.sh so I guess they were fixed
already.

http://lists.openembedded.org/pipermail/openembedded-core/2013-October/084905.html

You can use the same script to keep your new toy busy for a while :).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  parent reply	other threads:[~2013-11-21  0:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 21:05 Improving Build Speed Ulf Samuelsson
2013-11-20 21:29 ` Richard Purdie
2013-11-20 22:43   ` Ulf Samuelsson
2013-11-21  0:19     ` Martin Jansa
2013-11-21  7:15       ` Ulf Samuelsson
2013-11-21 12:53         ` Martin Jansa
2013-11-23 18:39         ` Nicolas Dechesne
2013-11-21  0:10   ` Martin Jansa [this message]
2013-11-21  8:04   ` Ulf Samuelsson
2013-11-21 13:53     ` Richard Purdie
2013-11-23 15:06       ` Ulf Samuelsson
2013-11-21 10:05 ` Burton, Ross
2013-11-21 11:51 ` Enrico Scholz

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=20131121001030.GV3708@jama \
    --to=martin.jansa@gmail.com \
    --cc=angstrom-dev@emagii.com \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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.