summaryrefslogtreecommitdiff
path: root/scripts/bitbake
Commit message (Collapse)AuthorAgeFilesLines
* scripts/bitbake: Update to help rebuild pseudo-nativeMark Hatle2012-03-281-5/+31
| | | | | | | | | | | | 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>
* scripts/bitbake: ensure user is in build directoryPaul Eggleton2012-03-141-0/+5
| | | | | | | | | 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>
* scripts/bitbake: pass through debug options to initial pseudo buildPaul Eggleton2012-02-211-1/+13
| | | | | | | | | | 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>
* scripts/bitbake: add a version >= 2.6 checkPaul Eggleton2011-12-151-0/+9
| | | | | | | | | 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>
* bitbake wrapper: exit if python v3 is detectedScott Garman2011-06-281-0/+11
| | | | | | | | | | | 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>
* scripts/bitbake: Only build tar-replacement-native when the build system tar ↵Richard Purdie2011-06-091-2/+19
| | | | | | version < 1.24 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Shift a few env bits into scripts/bitbakeChris Larson2011-03-211-0/+4
| | | | | | | | | | | 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>
* scripts/bitbake: add -g/--graphviz to NO_BUILD_OPTSChris Larson2011-03-211-1/+1
| | | | Signed-off-by: Chris Larson <chris_larson@mentor.com>
* sanity: detect if bitbake wrapper is not being used or pseudo is brokenPaul Eggleton2011-03-171-0/+3
| | | | | | | | | | | | * 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>
* tar-replacement-native: Add a target to replace the default tarRichard Purdie2011-02-211-2/+2
| | | | | | | | | | | | 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>
* scripts/bitbake: remove bashismsJoshua Lock2011-01-311-6/+6
| | | | | | | | | | | | 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>
* scripts/bitbake: If pseudo isn't in staging for some reason, force a build ↵Richard Purdie2011-01-281-7/+17
| | | | | | of it directly Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/bitbake: We only need pseudo-native in the sysroot, we can ignore ↵Richard Purdie2011-01-281-1/+1
| | | | | | any other pieces of the dependency tree Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/bitbake: Skip building pseudo if necessary.Lianhao Lu2011-01-051-3/+21
| | | | | | | Fixed [BUGID# 625]. Skip building pseudo if necessary by parsing the options to bitbake. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
* scripts/bitbake: Add wrapper script which ensures pseudo is built and availableRichard Purdie2010-12-171-0/+25
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>