<div dir="ltr"><div><div><div>I would agree that for classroom purposes, some of the best time savers are things like pre-fetching downloads to a local machine, pre-cloning kernel repos, and shared cache.<br><br></div>Also, IIRC several of the course lab examples (in the LF Yocto course) didn't quite work as expected (mostly kernel variables for some reason). I would probably recommend keeping things simple, as in teaching the config fragment approach (as is done in the kernel lab training thing). Can't remember what the all the issues were exactly as I normally build off master which gives me recurring deja vu, but keeping course materials current is always an ongoing issue for me...<br><br></div>Just my $.02 ...<br><br></div>Steve<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 25, 2015 at 12:41 AM, Robert P. J. Day <span dir="ltr"><<a href="mailto:rpjday@crashcourse.ca" target="_blank">rpjday@crashcourse.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, 25 Feb 2015, Richard Purdie wrote:<br>
<br>
> On Wed, 2015-02-25 at 03:25 -0500, Robert P. J. Day wrote:<br>
> > for the sake of reducing build time in the classroom, what are some<br>
> > of the potential (and relatively safe) candidates to add to<br>
> > ASSUME_PROVIDED for a build from scratch?<br>
><br>
> This path is fraught with danger to be honest. There are some things<br>
> which are "safe" like subversion and git but they don't make that much<br>
> difference to a build and there are not as many as you'd think.<br>
><br>
> The biggest difference you can make is an sstate cache you share amongst<br>
> the pupils. The time is spent:<br>
><br>
> a) building gcc<br>
> b) building libc<br>
> c) building gettext<br>
> d) building glib<br>
><br>
> each of these is a bottle neck which then opens up a new set of targets<br>
> as none of them are ASSUME_PROVIDED material.<br>
<br>
</span> ok, fair enough.<br>
<span class="im HOEnZb"><br>
rday<br>
<br>
--<br>
<br>
========================================================================<br>
Robert P. J. Day Ottawa, Ontario, CANADA<br>
<a href="http://crashcourse.ca" target="_blank">http://crashcourse.ca</a><br>
<br>
Twitter: <a href="http://twitter.com/rpjday" target="_blank">http://twitter.com/rpjday</a><br>
LinkedIn: <a href="http://ca.linkedin.com/in/rpjday" target="_blank">http://ca.linkedin.com/in/rpjday</a><br>
========================================================================<br>
</span><div class="HOEnZb"><div class="h5">--<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</div></div></blockquote></div><br></div>