summaryrefslogtreecommitdiff
path: root/scripts/poky-find-native-sysroot
AgeCommit message (Collapse)AuthorFiles
2011-04-20Rename the remaining poky-* scripts to oe-* or runqemu-*Richard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-20POKY_NATIVE_SYSROOT -> OECORE_NATIVE_SYSROOTRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2010-12-09Make poky-qemu and related scripts work with arbitrary SDK locationsScott Garman1
* No longer assume SDK toolchains are installed in /opt/poky * [BUGFIX #568] where specifying paths to both the kernel and fs image caused an error due to POKY_NATIVE_SYSROOT never being set, triggering failure of poky-qemu-ifup/ifdown * Cosmetic improvements to usage() functions by using basename Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2010-10-07Update meta-ide-support dependenciesScott Garman1
Using poky-qemu with our new tap networking and/or unfs support required too many additional build steps. This updates the meta-ide-support dependencies so all features are built and available to use. Specifically, this adds psuedo-native, qemu-helper-native, and unfs-server-native to the dependency chain for meta-ide-support. This fixes [BUGID #392] Also add poky-gen-tapdevs and remove runqemu-nfs from the qemu-helper-native recipe, and update some qemu control script error messages to suggest building meta-ide-support. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2010-09-07scripts: use the exported POKY_NATIVE_SYSROOT variableJoshua Lock1
Rather than trying to determine things through guess-work use the newly exported variables to determine where the native binaries reside and whether we are running in a build directory or not. Signed-off-by: Joshua Lock <josh@linux.intel.com>
2010-08-20poky-find-native-sysroot: helper script for locating the native sysroot pathScott Garman1
Various poky scripts make use of binaries from the native sysroot. This helper script can be used to reduce code duplication, and sets up some environment variables you can use to identify and obtain the correct filesystem path to the native sysroot. It works for both in-tree Poky setups as well as toolchain installations. Signed-off-by: Scott Garman <scott.a.garman@intel.com>