summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* apr: use ${HOST_SYS}-libtoolAndrew Gabbasov2012-01-301-1/+1
| | | | | | | | | | | | | libtool-cross uses ${HOST_SYS}- prefix while building and installing. In some cases that may be different from ${TARGET_PREFIX}, that is currently used in apr recipe. It's better to have them consistent. (From OE-Core rev: 61cedb87446a27ddaaa880a5f3296399def441df) (From OE-Core rev: 170d1fe5158eeb316009b2920b009da2c2dedae2) Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpam: add flex-native to DEPENDSAndrew Gabbasov2012-01-301-1/+1
| | | | | | | | | | | | | flex-native is required for building libpam. Although this dependency is now fulfilled indirectly through bison recipe, having an explicit one would be preferable. (From OE-Core rev: 14018608277fe62e2a662711ff6177c93e9bc153) (From OE-Core rev: 3a8ca44cbd31411934b6c873f75f1fb49167f93c) Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-setup-rpmrepo: use setup_tmpdir from runqemuPaul Eggleton2012-01-301-13/+14
| | | | | | | | | | | | Update the internal copy of setup_tmpdir in the oe-setup-rpmrepo script to be the same as the one in the runqemu script. (From OE-Core rev: 4a23c4dd5ab31d9642e5e49569d5c7ab77e97adf) (From OE-Core rev: 2174746ca6f480eb6387d91f9b3faf2581e816d3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts: use OE_TMPDIR instead of TMPDIR external variablePaul Eggleton2012-01-304-5/+16
| | | | | | | | | | | | | | | | On OpenSUSE within an X session, TMPDIR is set to the system temporary directory (/tmp) which is incorrect for these scripts. Thus, change runqemu and oe-setup-rpmrepo to use OE_TMPDIR from the external environment rather than TMPDIR. Fixes [YOCTO #1530] (From OE-Core rev: 4e24c10952c7a52af7f2447595fd484692d35534) (From OE-Core rev: 354497bf3e3bf68374875caa97d9b4fdcad74789) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: fix QA Warning on installed but not shipped staticdev fileswSaul Wold2012-01-301-7/+10
| | | | | | | | | (From OE-Core rev: 62ce8f96626e061e03ca49896716bbb133721ee0) (From OE-Core rev: 59f80f70c5ff6c62143b7bad5a67d5508b388d29) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: qt4: fix postprocessing of pkg-config filesSimon Busch2012-01-303-5/+3
| | | | | | | | | | | | | | | When building qt4-embedded the generated and cleaned pkg-config files for qt are wrong. The Cflags variable contains something like ${includedir}/qtopia/QtCore where ${includedir} is already /usr/include/qtopia/QtCore. This patch reverts the fix up of the Cflags variable implemented in do_install. (From OE-Core rev: b40b9c024be5e1ec81a31961158b3e6b529acfe0) (From OE-Core rev: 960318ebd271ad5330a0863047927ab827b5e107) Signed-off-by: Simon Busch <morphis@gravedo.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Fix QA warningsRichard Purdie2012-01-301-6/+12
| | | | | | | | | | | | | | | This fixes two QA warnings: a) Debug files being contained in the main package (by adding an appropriate FILES expression) b) Stop hardcoding the RPATH in the nativesdk case since our path is on the loaders default search path (From OE-Core rev: 1577975202437f8f89ef24a5e4d3f6c6c8a88c5c) (From OE-Core rev: 0c345e7aa83196e55cd554a958690e4cc261ef16) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sqlite3: Fix nativesdk packaging/QA warningsRichard Purdie2012-01-302-2/+2
| | | | | | | | | | | | | | When building sqlite3-nativesdk, there was a warning about debug files in the main package. This was due to the order of items in PACKAGES with -dbg after the main package which breaks an assumption native.bbclass makes. Changing the order fixes the packaging problem with no change to the normal target packaging. (From OE-Core rev: 4f5fdc4dc14d287d301069024ddec9cb65d68f7f) (From OE-Core rev: 8f2ff09f0da21e83ddfb8049bf7ddece94eb6893) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* grub: Fix insane/QA architecture warningRichard Purdie2012-01-301-1/+1
| | | | | | | | | | | | There is QA warning about this package for an architecture mismatch but this is inappropriate in this case since the bootloader needs 32 and 64 bit code. We therefore flag the QA check to be skipped. (From OE-Core rev: 43723e19eb5a6119c7546dc812428e792999a928) (From OE-Core rev: f31c0b804b04cd1ae9ea7251164fd1345697c72b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fix two QA issuesRichard Purdie2012-01-302-0/+6
| | | | | | | | | | | | | a) There is a QA warning from a .so being present in a main package. In the case of the plugin library for gcc, this is allowed. b) Remove the unwanted libiberty.a file with the strange path. We don't need/want this and this removes an unpackaged file warning. (From OE-Core rev: ca36a3edf9cede9fa0d73ba1a9538ab467cb5e3c) (From OE-Core rev: 974677d32e0af74fab58d1b12b8d786b67323c5a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libffi: really populate -dev packageDmitry Eremin-Solenikov2012-01-301-0/+3
| | | | | | | | | | | | | | | As per gcc PR 11147, libffi installs headers into a target dependent place (/usr/lib/....). Include a rule to include those files into libffi-dev package. Reference: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11147 (From OE-Core rev: 684a4b517d13884c315688967fadd5e6a4845b71) (From OE-Core rev: 5cb756227b12e0d537430a527c51033572fb627e) Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gconf-dbus: packaging fixupDmitry Eremin-Solenikov2012-01-301-1/+3
| | | | | | | | | | | | Behave more like plain gconf: include a dtd and .la files into -dev package. (From OE-Core rev: 9e962c1b4c8e5a3352f5e2b7dc162aeac1335b3a) (From OE-Core rev: 53951cffc4253850b9b0d6e24f932a9106dfafef) Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: include libgcov.a into libgcc-dev packagelumag2012-01-304-2/+4
| | | | | | | | | | | | | | First, this lib is usefull for coverage analysis-enabled building. Second, this fixes the warning about unpackaged files in libgcc recipe. (From OE-Core rev: 2a807a98d8be3f486e703321773db32657c71d9e) (From OE-Core rev: 651e6ee7d1ba729ed0bb5e9ede5975582d9941bf) Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: fix possible problems with nscd compilation during eglibc-nativesdk buildDmitry Eremin-Solenikov2012-01-303-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | Long time ago a066e7ca90a28d5681c5fa895a29e999ed7c88b was committed to address possible problems with compilation of nscd during eglibc-nativesdk build. Problems were related to the way gcc searches for headers to check if it should enable it's own stack smash protection bits or it can relay on eglibc for it. However after 934d38530c9a67562e53d4034aee5531f0f26750 things got broken, as for gcc-crosssdk-intermediate packages: 1) EXTRA_OECONF is ignored 2) headers are installed in a different location than expected by that patch. This results in eglibc-nativesdk build broken on some systems (e.g. mine Debian x86_64 squeeze). Fix that by providing with-headers options to crosssdk-intermediate gcc configuration. (From OE-Core rev: 63494d638b7a9b88a5b7d7a02d2afcb3aa0fa064) (From OE-Core rev: b4a686061f27f663321674fb42aa93dbd20c5b3a) Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc-create-env-native: provide the script right in the treeDmitry Eremin-Solenikov2012-01-303-109/+194
| | | | | | | | | | | | There is no point in downloading a tarball with no clear upstream (other than icecc itself) and then patching it. Rather put new script in the source tree. (From OE-Core rev: 409fa8ca4d37ad407faaa2a8935e9d2bb89776c9) (From OE-Core rev: e68d1d5117be9631db644b70308e7360a9d76a3a) Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: change ccache path to use MULTIMACH_HOST_SYSDmitry Eremin-Solenikov2012-01-301-1/+1
| | | | | | | | | | | | | | | | | Currently if I build packages for several targets (e.g. for armv5te tosa and for armv7a beagleboard) oe will use single ccache dir for both of those targets: build/ccache/arm-oe-linux-gnueabi. However those targets use different opcodes, different features and binaries created for one of those targets wont't run on the lower one. So use MULTIMACH_HOST_SYS for ccache dir, so that it uses something like build/ccache/armv5te-oe-linux-gnueabi dir. (From OE-Core rev: 982373006a98cf2303514badd1cfb692108408c0) (From OE-Core rev: 9d460e31b6b45b30b39587503d655aa2a418cbc3) Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnome-doc-utils: Prepend PKG_CONFIG_SYSROOT_DIR to the path returned from ↵Khem Raj2012-01-302-2/+41
| | | | | | | | | | | | | | | PKG_CONFIG If we build say gnome based image on a build system which does not have gnome e.g. kubuntu then packages like gedit do not build since it uses gnome files from host system which are non existent on kubuntu (From OE-Core rev: 7b18b3c96634e40abf690a7ec72562389b0e6c23) (From OE-Core rev: a413f3adcfb8245550067c1c2a3197817e631ffe) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools.bbclass: Set the dynamic linker search path for libtool correctlyRichard Purdie2012-01-302-0/+5
| | | | | | | | | | | | | | libtool obtains the search path from /etc/ld.so.conf and hardcodes /usr/lib and /lib. This results in host contamination and variable sets of RPATH values ending up in binaries. By exporting the correct values for all autotools recipes we avoid this. (From OE-Core rev: 93e595d5c89ebacdb8d1e6fcfe6f58fe2d30de28) (From OE-Core rev: 5e41e0973a9be890ac310e1bbf465fcd08b0add5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* matchbox: Upgrade SRCREV to reflect recent accpeted patches by upstreamZhai Edwin2012-01-3013-144/+17
| | | | | | | | | (From OE-Core rev: 33a1a05ef988c69f8ff8e38c6723922082e5d1aa) (From OE-Core rev: 1194935707f4acd9029b36769bc0320ba0a90163) Signed-off-by: Zhai Edwin <edwin.zhai@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cups: Fix recipe to use the correct cups directoriesMark Hatle2012-01-302-7/+15
| | | | | | | | | | | | ${libdir} is not used, instead they use a common ${exec_prefix}/lib directory structure for helpers, filters, renderers, etc. (From OE-Core rev: 24ae432b1a3906956381d83c1984687e45c5a1d1) (From OE-Core rev: 72da8109de9c2b1e237655706cdf4de447d38393) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eglibc-2.12: Fix build on powerpc/603eKhem Raj2012-01-302-1/+28
| | | | | | | | | | | | | | | | | | We pass --with-cpu to eglibc now. Which breaks the configure for cpus that it does not support We add support for ppc603e which gets 2.12 building for qemuppc. (From OE-Core rev: 465a988e2370ec377875b599045f2a7bad913ac6) (From OE-Core rev: f6dbd42382d980d90f3e64a94178a0050af537cf) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Conflicts: meta/recipes-core/eglibc/eglibc_2.12.bb
* gcc: include plugin-related headers into packaged SDKDmitry Eremin-Solenikov2012-01-303-2/+3
| | | | | | | | | | | | Include headers necessary to compile gcc plugins into cross-canadian gcc packages. (From OE-Core rev: d12aa92b3dac1109d510e7b6f74055d1ab927817) (From OE-Core rev: 51c96c98fca5a4a51cb38a6442ab9b4a03938721) Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs: include devtools scriptsDmitry Eremin-Solenikov2012-01-301-1/+2
| | | | | | | | | | | | Some scripts are necessary to develop programs with libcom_err and libss. Include those into e2fsprogs-dev package. (From OE-Core rev: 46332c2313abb273f6fc889fac4daa91cf43faa3) (From OE-Core rev: f1f22acd15591e5394254441c4364899875a0fbc) Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0: include glib-gettextize stuffDmitry Eremin-Solenikov2012-01-303-3/+3
| | | | | | | | | | | | glib-utils already includes glib-gettextize program. Include some files necessary for glib-gettextize to work. (From OE-Core rev: c98356e9c46cd28b7ca8e84fe0ea56dc6d812a8d) (From OE-Core rev: 0f0d5c7d980400bb45e78b7f178844c5a6dbf630) Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-lib: Don't use versioned symbols on uclibc builds as it causes strange ↵Daniel Lazzari2012-01-301-0/+2
| | | | | | | | | | | | | hangs alsa-lib: Don't use versioned symbols on uclibc builds as it causes strange hangs. Taken from oe-classic. (From OE-Core rev: b354eb957ce08ac7814ce46c13ca3a8449b4063a) (From OE-Core rev: 16852546234a252103337414fe536a3b97443539) Signed-off-by: Daniel Lazzari Jr <dlazzari@leapfrog.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: v3.0.10 + rt27Bruce Ashfield2012-01-302-13/+14
| | | | | | | | | | Updating the BSP base to the kernel.org v3.0.10 baseline and importing the latest stable rt27 release. (From OE-Core rev: e8aa8fe6e299104d4eb6da16134272a1dc7e929b) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: change SRC_URI to 3.0 maintenance kernelBruce Ashfield2012-01-302-4/+4
| | | | | | | | | | | | The 3.0 yocto kernel is updated for both new feature development and for maintenance purposes. The maintenance kernel repository takes updates once they have been applied to the development repository and have been deemed safe/suitable for point releases. (From OE-Core rev: 0b6eedfe26fca031e84543cab92b20e121364fb7) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* README.hardware: declare support for BeagleBoard xM rev BPaul Eggleton2012-01-301-1/+1
| | | | | | The BeagleBoard xM revision B has been tested (by me, if nobody else.) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
* README.hardware: update atom-pc instructionsPaul Eggleton2012-01-301-17/+9
| | | | | | | | | The -live and -directdisk images have been superseded in the Yocto Project 1.1 release, so update the instructions for atom-pc relating to this change. Also fix a couple of other minor atom-pc related capitalisation. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
* poky: set linux-yocto-rt preferred version for qemu machinesJoshua Lock2012-01-301-0/+5
| | | | Signed-off-by: Joshua Lock <josh@linux.intel.com>
* local.conf.sample.extended: Fix bug 1674Xiaofeng Yan2012-01-301-0/+3
| | | | | | | | | | | | | [YOCTO #1674] local.conf.sample.extended: An image based on gtk+-directfb don't need x11 for DEFAULT_FEATURES Remove "x11" from DEFAULT_FEATURES and add "directfb" to it because someone could don't need x11 in their project, perhaps gtk over directfb will meet his reqirement. (From OE-Core rev: 5def790bdecd2726692b40a57bc12c8bdfea9179) Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* machine/atom-pc: enable soundJoshua Lock2012-01-301-1/+1
| | | | | | | Add alsa to the MACHINE_FEATURES - looks like this was an oversight. Signed-off-by: Joshua Lock <josh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ui/crumbs/hobprefs: trigger a reparse after changing IMAGE_FSTYPESJoshua Lock2012-01-301-0/+1
| | | | | | | | | | | | | | | As reported on the mailing list[1] when changing IMAGE_FSTYPES through the hob preferences a reparse is required before the changes will be picked up by the system. This patch sets the reload_required property of the class to true when the image types have been modified to ensure the reparse is triggered. 1. https://lists.yoctoproject.org/pipermail/yocto/2011-December/006002.html (Bitbake rev: 6c0babf08909307ab69a66ed06e77e8818b2a8c5) Signed-off-by: Joshua Lock <josh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ui/crumbs/runningbuild: handle InvalidTask eventsJoshua Lock2012-01-301-0/+4
| | | | | | | | | | | | The knotty UI just ignores these and so should RunningBuild, if these events aren't handled the UI appears to hang. Fixes [YOCTO #1665] (Bitbake rev: 540ba78075bd525776aa23bf38bee66350c66534) Signed-off-by: Joshua Lock <josh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* siggen.py: If both sigs have a variable in it's whitelist then don't say ↵Matthew McClintock2012-01-301-3/+3
| | | | | | | | | | | | | it's changed Some BB_HASHBASE_WHITELIST variables are in the lists of variable dependencies for signatures. Ignore those differences in lists since this difference does not matter (Bitbake rev: 71b53a3f0766ca464560a1f6a449f9424fbdf7ae) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update and fix bitbake-runtaskRobert Yang2012-01-301-66/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Since bitbake switched back to the fork instead of the exec model, it no longer used bitbake-runtask and the code has suffered some bitrot. bitbake-runtask is a useful tool for excuting the task without the scheduler of bitbake, so that the external tool can invoke it easily. It also provides a useful example of how to invoke exec_task() with low overhead without a lot of the bitbake threading/UI overhead. Significant changes: * This patch changes the argument order so that the commonly used and mandatory arguments come first. * The taskhash file and dryrun options are now optional * It now uses the bitbake logging mechanisms to provide processed logging output to the console. * The process handling to do with stdout/stderr redirection are removed since they're no longer required. [YOCTO #1229] RP: Logging updates to the patch based on Roberts original patch Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/siggen.py: Don't backtrace if the taskhash data isn't presentRichard Purdie2012-01-301-2/+2
| | | | | | | | | | This allows the code to safely fall back to dumping the basehash data if the taskhash data isn't present for some reason. We could effecitvely obsolete the runtime option and use this approach instead exclusively. (Bitbake rev: 5ace320ccc01f4e326f90b7ba060dcbff3380dca) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build.py: Be determistic about a function's cwdRichard Purdie2012-01-301-2/+1
| | | | | | | | | | | | | | | | | There is a subtle but nasty problem that a function's cwd can vary depending on whether ${B} (often ${S}) exists before the funciton is called or not. Most functions in the system can cope with this but its bad practise and I've just witnessed build failures resulting from this during image generation from bootimg.bbclass. I also suspect this could explain some odd fetcher behaviour witnessed in the past. This change ensures we always call funcitons with a specific build directory making things deterministic. (Bitbake rev: ef0888f83fa4408eb768257d7e03700202faad18) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cooker.py: Allow the -e option to work with virtual classes and -bRichard Purdie2012-01-301-1/+3
| | | | | | | | | | | | | Using bitbake -e -b virtual:xxxx:/path/to/the.bb would result in zero matches since the virtual:xxxx piece wasn't being processed. This adds in the necessary functionality to handle it correctly. [YOCTO #1793] (Bitbake rev: bd5a727c8447bcb747c1d2463b7de2ab6d21a7de) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Nothing uses USERNAME, remove it - can cause sstate-cache conflictsMatthew McClintock2012-01-301-1/+0
| | | | | | | | | | USER is the correct variable to use, also this can affect sstate cache as well. (Bitbake rev: d7f9edda65dae2e046871afa275c5a51dff48fc4) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* codeparser: silence non-literal warnings for vardepsChristopher Larson2012-01-303-9/+37
| | | | | | | | | | If the vardeps flag is not None, we now silence the warnings about non-literal usage for that variable. (Bitbake rev: e724b9f417d1baf898f5afc6376c73c1a2ad8db9) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* codeparser: drop expand trackingChristopher Larson2012-01-301-11/+0
| | | | | | | | | | | | | | | | | | | | | | There are two usual cases involving bb.data.expand: - Calling it with a string literal -- "bb.data.expand('${FOO}/${BAZ}/bleh', d)". - Calling it on getVar results (legacy) -- "bb.data.expand(bb.data.getVar('FOO', d), d)" Nothing in any of the usual layers uses it in any other way, and I'm having trouble coming up with any real use cases beyond this. The first of the above cases is already tracked, via the expandWithRefs called on the python code string. The second didn't emit a warning anyway, since the getVar was already handled. Given this, I see no reason for us to maintain explicit expansion tracking. Further, we weren't using its results anyway (the var_expands member). (Bitbake rev: 405dfe69e6a608826e599ebf2f83ef8cf5083b96) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* codeparser: accept a name for better messagesChristopher Larson2012-01-303-11/+13
| | | | | | | | | | | | | | | | | | | | - If a name is passed to the parser, prepend the messages with "while parsing <name>:". This gives a bit more context. - Tweak the warning messages slightly (they had to be altered anyway to inject the variable being parsed). Before: DEBUG: Warning: in call to 'bb.data.getVar': argument ''%s' % var' is \ not a literal After: DEBUG: while parsing emit_pkgdata, in call of bb.data.getVar, argument \ ''%s' % var' is not a string literal (Bitbake rev: 1060193ae4d54e667735dbff5d1d2be49a3f95c9) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* codeparser: simplify how we compare the called node namesChristopher Larson2012-01-301-52/+20
| | | | | | | | | | | | | | With the previous method, using the compare_name methods, we split the requested match name by '.', reversed it, then compared them piecemeal during the node traversal. The new method walks the nodes and hands back the name of what's being called, and then we check that. This also consolidates the two different implementations of traversal of the attribute/name nodes (one in compare_name, one for the execs). (Bitbake rev: 84e535b5165c7e936c5b1486bdf4626ed3649f5f) Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* codeparser: merge the nested python parsing classesChristopher Larson2012-01-301-102/+87
| | | | | | | | | | The split is even less necessary now that we use ast.walk rather than an actual NodeVisitor subclass. (Bitbake rev: d6c44fac184abae8395bfa7078f06675218aa534) Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* data/siggen: Add vardepvalue mechanism to allow the variable dependency code ↵Richard Purdie2012-01-302-13/+17
| | | | | | | | | | | | | | | | | | | | | | | to be forced to specific values We have a problem if we want to inject specific information into the variable dependency code. There are cases for example where we want a dependency on the value of X but it doesn't matter how X was constructed or what dependencies it might have had, we only care about the absolute value. With the current code, its near enough impossible to do this. This patch adds such a mechanism so the user can trigger this with code like: baselib[vardepvalue] = "${baselib}" It also refactors some of the code so we do variable lookups once instead of doing this in two different functions. [YOCTO #1583] (Bitbake rev: 6c879b44ccf42dc73fe4467076e114700d7ba81b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* fetch2: Improve uri_replace to handle paths with no trailing '/'Richard Purdie2012-01-301-3/+10
| | | | | | | | | | | | | | | | | | | | | | Currently if you specify a mirror like: file://.* http://linux.freescale.net/yocto/sstate-cache it won't work as you expect whilst: file://.* http://linux.freescale.net/yocto/sstate-cache/ will since it has the trailing slash. This patch handles both cases correctly. It also adds some debug to the uri_replace function since its near impossible to debug it without some kind of output. [YOCTO #1578] (Bitbake rev: a0246bf09c93bb657eaf6ba61d090b247ed33640) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqueue.py: Fix debug message to reference the correct taskRichard Purdie2012-01-301-1/+2
| | | | | | (Bitbake rev: 035c673c463ca450245acf824e7b7e8f889bdc89) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* fetch2/local: Don't default to files in DL_DIR for file:// urlsRichard Purdie2012-01-301-3/+1
| | | | | | | | | | | | | | | Defaulting to any file in DL_DIR as the first match for a file:// url doesn't make much sense and can lead to unexpected results. This patch changes the logic so this is the last fallback location instead. Whether it should be using DL_DIR at all for this is a good question but something for another patch. [YOCTO #1710] (Bitbake rev: 5597a68fac0954c682b67471722c2643e2415f99) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* siggen.py: sort task hash depedencies with basepathMatthew McClintock2012-01-301-11/+14
| | | | | | | | | | | | | | | Without this patch the tash hash dependencies can be in a order that is dependent upon directory/filesystem layout. With this change the data is sorted the same regardless. Without this the dependent hashes could be in different orders on different systems and consequently final md5 hash would differ as well even though nothing else changed. (Bitbake rev: 9a2029899c946ce9aa8adbc85f2cfe7a85b92182) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-14 14:48:57 +0000