From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: on current linux distros, what are potential candidates for ASSUME_PROVIDED?
Date: Wed, 25 Feb 2015 03:41:02 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1502250340130.25049@localhost> (raw)
In-Reply-To: <1424853407.26813.29.camel@linuxfoundation.org>
On Wed, 25 Feb 2015, Richard Purdie wrote:
> On Wed, 2015-02-25 at 03:25 -0500, Robert P. J. Day wrote:
> > for the sake of reducing build time in the classroom, what are some
> > of the potential (and relatively safe) candidates to add to
> > ASSUME_PROVIDED for a build from scratch?
>
> This path is fraught with danger to be honest. There are some things
> which are "safe" like subversion and git but they don't make that much
> difference to a build and there are not as many as you'd think.
>
> The biggest difference you can make is an sstate cache you share amongst
> the pupils. The time is spent:
>
> a) building gcc
> b) building libc
> c) building gettext
> d) building glib
>
> each of these is a bottle neck which then opens up a new set of targets
> as none of them are ASSUME_PROVIDED material.
ok, fair enough.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2015-02-25 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 8:25 on current linux distros, what are potential candidates for ASSUME_PROVIDED? Robert P. J. Day
2015-02-25 8:36 ` Richard Purdie
2015-02-25 8:41 ` Robert P. J. Day [this message]
2015-02-26 19:03 ` Stephen Arnold
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=alpine.LFD.2.11.1502250340130.25049@localhost \
--to=rpjday@crashcourse.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox