summaryrefslogtreecommitdiff
path: root/meta/classes/pkgconfig.bbclass
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2012-02-23 20:58:47 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-02-24 17:12:00 +0000
commite3b6537cc7931636ab11ae6ed2c8fbaad9da91bc (patch)
tree5e2bb9032939fac2e58a921c7e54430f404a4948 /meta/classes/pkgconfig.bbclass
parent94c52d68fc2ce258bcc5b0978ac73413480a1a93 (diff)
downloadopenembedded-core-e3b6537cc7931636ab11ae6ed2c8fbaad9da91bc.tar.gz
openembedded-core-e3b6537cc7931636ab11ae6ed2c8fbaad9da91bc.tar.bz2
openembedded-core-e3b6537cc7931636ab11ae6ed2c8fbaad9da91bc.tar.xz
openembedded-core-e3b6537cc7931636ab11ae6ed2c8fbaad9da91bc.zip
linux-yocto: improve checkout error handling and reporting
The typical workflow for linux-yocto simply uses a remote upstream repository (Whether it is mirrored or not), and in this case there are no issues with consistency in the format of the resository that is unpacked into the WORKDIR. When working with a local linux-yocto repository for kernel development the remote vs local branches is not always consistent between repositories. The suggested/documented workflow has always been to use a bare clone of linux-yocto, and use a second working tree repository for development. Changes flow from the working tree to the bare clone and then into the working directory for build. A common mistake that happens with this workflow is that the non-bare, working repository is used instead of the bare clone version. If a non-bare repository is reference by the SRC_URI, then the branches that are fetched into WORKDIR are not consitent. If the MACHINE and META branches are not present, cryptic build errors will result. To solve this problem, the checkout code has been changed in several ways: - works with a newly proposed 'bareclone' option to bitbake - detects if a bareclone is present in WORKDIR or not and adjustst the checkout accordingly. - if a non-bare clone is detected, machine and meta branches are checked. If they are not present, or can't be created a clear error message is produced - instead of manipulating the refs directly in the git tree, local tracking branches are (quietly) created for remote branches. Enabling a better workflow in the WORKDIR kernel repository. This has been tested with linux-yocto remote upstreams, local bare and non-bare respositories. All builds succeed or fail with clear error messages. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/pkgconfig.bbclass')
0 files changed, 0 insertions, 0 deletions