summaryrefslogtreecommitdiff
path: root/scripts/bitbake
AgeCommit message (Collapse)AuthorFiles
2013-05-21scripts/bitbake: Handle the case where git isn't installed cleanlyRichard Purdie1
Currently the user sees ugly errors if git isn't installed, this patch cleans up the code to correctly handle that case. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-02-15scripts/bitbake: Remove all instances of paths to a layer's scripts directory.Franklin S. Cooper Jr1
* Currently the assumption is made that only oe-core can include a scripts directory. * However, when other layers create a scripts directory the bitbake script freaks out causing a infinite recursive loop until it crashes. * Simply changing the regular expression to remove all instances of scripts path instead of just the first one fixes this problem. [Yocto Bug 3872] Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-08-28bitbake: compile tar-replacement firstlyRoy.Li1
Compiling tar-replacement or not is decided by version of host tar, if the host tar version is lower than 1.23, Compiling tar-replacement is needed. When doing popoluate tar-replacement sysroot to write the tar to sysroot, but writing is not finished. other packages probably use the being written tar to unzip file, which will lead to failure and report the below error: "bitbake_build/tmp/sysroots/x86_64-linux/usr/bin/tar: Text file busy" Now we compile tar-replacement firstly to ensure that a being written tar command will not be used. Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-07-31scripts/bitbake: unbreak the git version comparisonChristopher Larson1
With the current code, we're calling awk to do a floating point comparison between '1.7.0.4' and '1.7.5' (on an ubuntu 10.04 LTS machine). These clearly aren't proper floating point numbers, and the comparison is incorrect. It's returning true for 1.7.0.4 >= 1.7.5. Instead of using a floating point comparison for this, call out to python and let it do it. Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-18scripts/bitbake: Check the git-native version and build it if necessaryRichard Purdie1
We require git version 1.7.5 or later for the git remote --mirror=xxx syntax. If we have an older version of git, this patch ensure we build git-replacement-native. We add an alternative PROVIDES in the same way as tar-native to allow this script to trigger the build whilst still allowing git-native in ASSUME_PROVIDED. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-03-31scripts/bitbake: add/fix some commentsPaul Eggleton1
Add some comments explaining what this script does, fix one grammatical error in a comment and make the tar-replacement-native comment give the full reason why it is needed. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2012-03-31scripts/bitbake: allow switching between build directoriesPaul Eggleton1
The recent addition of the check to ensure the user was in their build directory disabled the ability to switch between build directories without re-running the build environment setup script. We can rely upon checking for conf/bblayers.conf instead, so use this check. This does allow BUILDDIR (which is normally set by the environment script) to be unset; however if it is set then it is assumed to be the correct build directory and will be used in the error message that is shown when we can't find conf/bblayers.conf. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2012-03-31scripts/bitbake: try harder to check if pseudo existsPaul Eggleton1
If pseudodone doesn't exist, we can get STAGING_BINDIR_NATIVE by calling bitbake -e and use that as the path to check for pseudo before we give up and try to build it explicitly first. This is useful for people who share TMPDIR between multiple build directories. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2012-03-28scripts/bitbake: Update to help rebuild pseudo-nativeMark Hatle1
Attempt to detect when pseudo-native has been updated. If it has been updated, or if the user is attempting an operation with pseudo-native in the name, force a build of pseudo-native, prior to running the main build. Note: This causes a build, then clean in the case of bitbake -c cleansstate pseudo-native Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-14scripts/bitbake: ensure user is in build directoryPaul Eggleton1
If the user is in any directory other than $BUILDDIR when the bitbake wrapper script is run, then show an error an exit. Fixes [YOCTO #2071]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2012-02-21scripts/bitbake: pass through debug options to initial pseudo buildPaul Eggleton1
If you specify -D or -v options to the bitbake wrapper script, and the initial pseudo build needs to be done, it's useful to pass these options through to that command so that you can debug the initial pseudo build as well. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-12-15scripts/bitbake: add a version >= 2.6 checkPaul Eggleton1
Unfortunately we now have code in BitBake which is parsed before the current version check and is incompatible with Python < 2.6. Rather than fixing this and being eternally vigilant for >= 2.6 feature usage, just add a version check to the wrapper script. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2011-06-28bitbake wrapper: exit if python v3 is detectedScott Garman1
Make sure we're not using python v3.x. This check can't go into sanity.bbclass because bitbake's source code doesn't even pass parsing stage when used with python v3, so we catch it here so we can offer a meaningful error message. This fixes bug [YOCTO #1128] Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-06-09scripts/bitbake: Only build tar-replacement-native when the build system tar ↵Richard Purdie1
version < 1.24 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-03-21Shift a few env bits into scripts/bitbakeChris Larson1
This attempts to separate the bits we *require* to run bitbake with oe-core via the wrapper script, and which are independent of the build environment (PSEUDO_DISABLED, PSEUDO_BUILD, BBFETCH2) from those which are more particular to poky-init-build-env's way of setting things up (e.g. adding MACHINE to BB_ENV_EXTRAWHITE, relying on OEROOT, etc). This should make it easier to use scripts/bitbake with non-standard workflows. Signed-off-by: Chris Larson <chris_larson@mentor.com>
2011-03-21scripts/bitbake: add -g/--graphviz to NO_BUILD_OPTSChris Larson1
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2011-03-17sanity: detect if bitbake wrapper is not being used or pseudo is brokenPaul Eggleton1
* Shows a warning during sanity checking if the scripts/bitbake wrapper is not being used * Check to see if pseudo is working during sanity checking, and if it isn't an error occurs (if we are using the wrapper script and pseudo has been built; otherwise it is a warning). Fixes [YOCTO #653] Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2011-02-21tar-replacement-native: Add a target to replace the default tarRichard Purdie1
tar < 1.24 has symlink issues where extracting a tar archive containing a symlink to a directory where that symlink already exists will cause the symlink to be dereferenced. If that target doesn't exist tar can fail with a permissions error. Since we need to be able to do this for packages containing symlinks like xorg-minimal-fonts and eglibc, we have to ensure a tar 1.25 is available early in the build process. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-31scripts/bitbake: remove bashismsJoshua Lock1
As the BitBake script is the initial entry point for the system we need to ensure it can run in as many places as possible, including systems which aren't yest optimally configured for running Poky. Remove some bashisms from the script so that it can run under Dash. Pointers from: https://wiki.ubuntu.com/DashAsBinSh Errors before this patch: http://pastie.org/1502136 Signed-off-by: Joshua Lock <josh@linux.intel.com>
2011-01-28scripts/bitbake: If pseudo isn't in staging for some reason, force a build ↵Richard Purdie1
of it directly Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-28scripts/bitbake: We only need pseudo-native in the sysroot, we can ignore ↵Richard Purdie1
any other pieces of the dependency tree Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-05scripts/bitbake: Skip building pseudo if necessary.Lianhao Lu1
Fixed [BUGID# 625]. Skip building pseudo if necessary by parsing the options to bitbake. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
2010-12-17scripts/bitbake: Add wrapper script which ensures pseudo is built and availableRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>