From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Changelog for 1.3
Date: Thu, 11 Oct 2012 12:22:05 +0100 [thread overview]
Message-ID: <2995833.IARlncBIop@helios> (raw)
Hi folks,
I've put together a list of medium to high-level changes based on
browsing through the commits for the release:
- Improved terminal UI which makes it easy to see the tasks that are currently executing, and avoids burying any warnings that are printed
- Eliminated intermediate step when building cross compiler toolchain
- SDK is now relocatable
- Large number of usability improvements in the Hob image building UI
- Upgraded eglibc to version 2.16
- Upgraded gcc to version 4.7
- Added yocto-bsp script for automating the initial parts of creating a new BSP
- Python functions now consistently use four spaces for indentation - no more having to try to match the mix of tabs and spaces in your recipes
- Disabled sharing shared state between machines using different distros by default to avoid glibc version problems
- Fixes to allow qemu-native to be built on host systems without X11 (i.e. for console use only)
- Enabled python and perl scripting for perf as well as text-mode UI
- Added ability to produce a companion SDK together with an image
- Allow forcing the rebuilding of a recipe (new -C and improved -f options)
- Enabled EFI in grub installer
- Mesa can now provide GLES accelerated graphics without X11
- Added script for producing "bootcharts" from buildstats so you can see the timeline of the build
- Checksums for local files referred to in SRC_URI are now included in task signatures so that changing their contents causes the relevant tasks to be re-executed
- Extended bitbake-diffsigs to look up signature files from task and recipe name, and trace back recursively through dependent task changes
- Moved from module-init-tools to kmod
- Added create-recipe script to automate some of the parts of creating a brand new recipe
- Buildhistory improvements: better performance, track postinst/postrm scripts
- Added bin_package bbclass for recipes that package pre-built binaries
- Added doc-pkgs IMAGE_FEATURES feature to install all documentation
- Added class-* overrides - particularly useful for target/cross/crosssdk but works with all classes
- Reference hardware BSPs are now separate from Poky reference distro configuration
- nativesdk is now a prefix rather than a suffix, simplifying packaging in nativesdk recipes greatly
- Detect and warn if files in the sysroot are potentially written to by multiple recipes
- Automatic launching of "screen" within terminal for devshell/patch resolution
- task-* recipes renamed to packagegroup-* and tidied up significantly
- Improved mirror handling - allow mirrors of mirrors; handle errors more gracefully
- Reduced dependencies between debugging symbol packages
- Significant cleanup of X server recipes
- Start to add regression tests for BitBake
Is there anything that belongs here that I have missed? I know we've done a
lot of other bugfixes and package upgrades, we're really after the
highlights.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next reply other threads:[~2012-10-11 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 11:22 Paul Eggleton [this message]
2012-10-11 13:11 ` Changelog for 1.3 Burton, Ross
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=2995833.IARlncBIop@helios \
--to=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.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.