[yocto] [poky] Major feature changes for the next release - merging very soon

Koen Kooi koen at dominion.thruhere.net
Tue Jan 25 10:34:04 PST 2011


Op 25 jan 2011, om 14:57 heeft Richard Purdie het volgende geschreven:

> As has been mentioned in other emails we're working on some major
> enhancements for the next release. Several components of these are now
> ready for merging to the master branch. These include:
> 
> * Rework of the compiler bootstrap process
> 
> If you've ever tried to run "bitbake eglibc -c clean;bitbake eglibc" or
> any of the gcc components you'll have run into issues with the compiler
> bootstrap process overwriting files. This also causes problems for
> sstate as it doesn't get on well with two sstate archives providing the
> same file.
> 
> The changes we have queued split the intermediate components into a
> separate sysroot so no files are overwritten and the whole process is
> less fragile and more robust. Each gcc-cross step (initial, intermediate
> and final) also stage binaries in separate locations.
> 
> * Changes to sysroot structure
> 
> We now support creating a sysroot per machine target rather than the
> original multimachine approach we have used. This means packages with an
> "all" architecture can be safely installed into the sysroot and used
> correctly fixing bugs in that area and it also allows machines like
> emenlow which have separate graphics components to build and work
> correctly yet be able to share builds with other machines like atom-pc.
> 
> If you change machine and the machine you change to shares a core
> architecture with a previous build, the components from that previous
> build will be used to construct a new sysroot using the sstate prebuilt
> packages.
> 
> The branch I'm planning to merge very soon with these features is:
> 
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=rpurdie/tt-bootstrap

For a single machine:

NOTE: package console-image-1.0-r0: task do_rm_work_all: Succeeded


Now building it incrementally for a different machine



More information about the yocto mailing list