summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* classes/recipes: More optimal DISTRO_FEATURES referencesRichard Purdie2013-12-0516-75/+54
| | | | | | | | | Using the contains function results in more optimal sstate checksums resulting in better cache reuse as we as more consistent code. (From OE-Core rev: 9c93526756e7cbbff027c88eb972f877bcb1f057) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eglibc-options: Rewrite so it benefits from bitbake's contains handlingRichard Purdie2013-12-051-85/+119
| | | | | | | | | | | Having eglibc rebuild every time DISTRO_FEATURES changes is suboptimal. This rewrite takes advantage of bitbake's understanding of the contains function so this doesn't happen. The code is marginally uglier but is worth the benefit in fewer libc rebuilds. (From OE-Core rev: 9a272ee6d72fc727a2dfe660ceded560a9f1ae88) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa/selftest/base, scripts/oe-selftest: fix wrong remove path and do a ↵Stefan Stanacar2013-12-052-1/+13
| | | | | | | | | | | | | | | | complete cleanup at the end The script should clean-up all the .inc files that might have been created by tests regardless of the outcome or if the script is interrupted. (currently the last test will leave a conf/selftest.inc around, even if it's not included anywhere) Also fix delete_recipeinc to actually delete what's supposed to. (From OE-Core rev: 6008745c56800e0f5f01a756be0701cebd9de4ae) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qt4: fixed dependency on icuEnrico Scholz2013-12-052-2/+2
| | | | | | | | | | | | | | | | | | | | | | Commit 46dcec6fd455584d9b5d0d7ff1e5b36fbe5a2d62 added 'icu' to DEPENDS in qt4-x11 only, but enabled icu globally in qt4.inc. This breaks build of qt4-embedded because this recipe does not have such a DEPENDS but uses qt4.inc: | icu.cpp:42:28: fatal error: unicode/utypes.h: No such file or directory | #include <unicode/utypes.h> | ^ | compilation terminated. | make: *** [icu.o] Error 1 Patch moves the 'icu' dependency into qt4.inc. (From OE-Core rev: adb6e64d69fc947f2c8fa708dcbe854fd2b574f8) Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Cc: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0-plugins-bad: add PACKAGECONFIG for librsvgRoss Burton2013-12-051-3/+1
| | | | | | | (From OE-Core rev: 667f1e5cb4e24cd868c8fcb6e434e70cf9383c87) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0-plugins-bad: respect directfb DISTRO_FEATURERoss Burton2013-12-051-1/+2
| | | | | | | (From OE-Core rev: f939ca25d4fbe83142b4e9f2671c96fb5f78d2ac) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: Add entry for opensslSaul Wold2013-12-051-0/+1
| | | | | | | | | | | | | | | | | | | | | | It seems we might be stumbling over an obscure linkage issues possibly similar to http://marc.info/?l=openssl-dev&m=130132183118768&w=2 This issue appears for x86-64 systems with the PIE related compiler flags. libcrypto.a(cryptlib.o): relocation R_X86_64_PC32 against symbol `OPENSSL_showfatal' can not be used when making a shared object; recompile with -fPIC The error suggests recompiling with -fPIC, but it is already compiled that way. Disable the PIE flags makes it work for now, I have posted to openssl ML [YOCTO #5515] (From OE-Core rev: 55e1c0e66fd16612016b3e415cbfa4e3051e5a8f) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* attr: Add patch tracking detailsNathan Rossi2013-12-051-0/+1
| | | | | | | | | | Add author tracking information to the attr patch added by commit b28f12a272a9e2f0c3084a58b91605acb05f58f8. (From OE-Core rev: 9b4bc93b7281d596b818533e013a13b3b69fea81) Signed-off-by: Nathan Rossi <nathan.rossi@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gst-plugins-good: Fix configure optionRichard Purdie2013-12-051-1/+1
| | | | | | | | | | | | Resolve the warning: WARNING: QA Issue: gst-plugins-good: configure was passed unrecognised options: --without-check (the option is no longer present) (From OE-Core rev: defe535f70369cbc0629853aebf044e846416216) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* leafpad: Fix configure flagsRichard Purdie2013-12-051-1/+1
| | | | | | | | | | | Remove the now unused gtktest configure flag and add one for the emacs option so we're deterministic. Resolves the warning: WARNING: QA Issue: leafpad: configure was passed unrecognised options: --disable-gtktest (From OE-Core rev: 522a8e8d332c162a923e8b880b36fc4b12320c87) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxkbfile: Remove obsolete configure optionRichard Purdie2013-12-051-2/+0
| | | | | | | | | | | | Resolves the QA error: WARNING: QA Issue: libxkbfile: configure was passed unrecognised options: --without-xcb (there is no such configure option any more) (From OE-Core rev: ef0b66f4a8522445ef8b6468660bf030849bab13) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Hob: check if warnings are related to package build1.6_M1.rc11.6_M1.final1.6_M1Valentin Popa2013-12-031-4/+4
| | | | | | | | | | | | | If warnings come from recipes parsing and not from package build, 'parent' object will be None; so don't update the color for it. [YOCTO #5621] (Bitbake rev: f9d24f55a5ffa9257e7ba3257be1210687513733) Signed-off-by: Valentin Popa <valentin.popa@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: fix package property dialog for changes to FILES_INFOPaul Eggleton2013-12-031-29/+15
| | | | | | | | | | The FILES_INFO structure is now much simpler, so remove all of the horrible mangling we had to do here in order to read it. (Bitbake rev: 11a664292064dbf76850bf21ba386f78a43a56b6) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: name package files list variables appropriatelyPaul Eggleton2013-12-031-11/+11
| | | | | | | | | | | This treeview code was obviously copy-pasted from one of the config dialogs and the variables were never renamed. Rename them now to improve readability. (Bitbake rev: 93b3ddad4396d757d1d0c199ac168f8b1a205fe3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: lib/bb/ui: handle PKGSIZE change to bytesPaul Eggleton2013-12-032-5/+4
| | | | | | | | | | PKGSIZE is now in bytes in pkgdata, so we need to treat it as such in the UI code for Hob / Toaster. (Bitbake rev: 3b5ff814cd4a3efa4b17c6b343ec39c9acca5c9e) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker/command/hob: Cleanup configuration init/reset functions and ↵Richard Purdie2013-12-034-53/+34
| | | | | | | | | | | | | | | | | | | | | | | | commands initConfigurationData and loadConfigurationData are similar functions, the only reason for them appears to be to be able to reset the pre/post configuration files. The current code is confusing and unmaintainable. Instead this patch creates a new Sync command which allows these to be explicitly set. The init and load functions can then be merged into one. There is then no need for a parseConfiguration command, we can simply reset the server to have the settings take effect. The reset fuction is not an instant value return and triggers an event so it should be an Async command, not a sync one. The number of calls for the set pre/post command is probably higher than it need be but someone with more familiarity with the hob code base can probably figure out the right places its needed (maybe just init_cooker?). (Bitbake rev: bae5210d7e048022f083361964ebec7daf1608f7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: Use BASEDATASTORE_TRACKING featureRichard Purdie2013-12-032-3/+1
| | | | | | | | Might as well use this functionality now we have it available. (Bitbake rev: cd7f4d85e3f187140d1bb0aecf82f657a8f8701a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: codeparser/data_smart: Optimise parsing speedRichard Purdie2013-12-032-7/+12
| | | | | | | | | | | | | | | | | | | | | The previous "contains" changes caused a ~3% parsing speed impact. Looking at the cause of those changes was interesting: * Use of defaultdict was slower than just checking for missing entries and setting them when needed. * Even the "import collections" adversely affects parsing speed * There was a missing intern function for the contains cache data * Setting up a log object for each variable has noticeable overhead due to the changes in the code paths uses, we can avoid this. * We can call getVarFlag on "_content" directly within VariableParse for a noticeable speed gain since its a seriously hot code path. This patch therefore tweaks the code based on the above observations to get some of the speed back. (Bitbake rev: fca802187a2a30686a8a07d2b6b16a3e5716e293) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ptest: ensure do_install_ptest_base task runs in fakeroot contextRoss Burton2013-12-031-0/+5
| | | | | | | | | | As this task is installing files into $D it needs to run inside pseudo so that special permissions and owners are preserved. (From OE-Core rev: 64f0a0bc408d8e32d5e795aeb9fffee0539f5e22) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk: verify executable or dynamically linked libraryyzhu12013-12-031-1/+1
| | | | | | | | | | | | When toolchain directory is changed to execute mode, some non-executable files or empty files are sorted. This will result in some errors. Thus when sorting executable files or dynamically linked library, additional conditions are to exclude non-executable files or empty files. (From OE-Core rev: c9d56308bfa9ee7f4a9b22eae86390626ddc1c35) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: handle CLOEXEC/NONBLOCK if unavailable on hostChristopher Larson2013-12-032-0/+93
| | | | | | | | (From OE-Core rev: d60cf44deb297119f97d7e792eae5ab01977e2fc) Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cairo: add/use packageconfig for valgrind supportChristopher Larson2013-12-031-0/+1
| | | | | | | | | | It was currently autodetecting. (From OE-Core rev: 68fc138d172d491e16d5e6f2fc21fc779c04b92f) Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python, python-native: fix PARALLEL_MAKEINST failureChristopher Larson2013-12-033-0/+21
| | | | | | | | | | | | | | When using make -j with the 'install' target, it's possible for altbininstall (which normally creates BINDIR) and libainstall (which doesn't, though it installs python-config there) to race, resulting in a failure due to attempting to install python-config into a nonexistent BINDIR. Ensure it also exists in the libainstall target. (From OE-Core rev: 54da47f3ddc1c009594744793060ffd09db3ad11) Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* quota: apply patch to obey tcp-wrappers configChristopher Larson2013-12-032-1/+77
| | | | | | | | | | | Without this, the tcpwrappers argument wasn't obeyed, and as such the build wasn't as deterministic as we'd prefer. (From OE-Core rev: 16bbdef239942276a1740a3b9dfe4e8c34a16b29) Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* subversion: fix build problem when sysroot contains '-D' or '-I'Chen Qi2013-12-032-0/+33
| | | | | | | | | | | | | | | | | If sysroot contains '-D' or '-I' characters, the SVN_NEON_INCLUDES and the corresponding CFLAGS will not get the correct value. This will cause build failures. This patch fixes the above problem. [YOCTO #5458] (From OE-Core rev: 7078397ef39de43244fca7e24683b2a83913cbbf) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image-mklibs: ensure sysroot is correctly set when calling gccNicolas Dechesne2013-12-031-0/+1
| | | | | | | | | | | | | | | | | | [YOCTO #2519] When getting gcc from sstate, it is possible to get a gcc with a bogus sysroot configuration, as discussed in [1] or in [YOCTO #2519]. mklibs script will eventually call gcc, so we need to make sure that it provides gcc with the right sysroot location. [1] http://lists.openembedded.org/pipermail/openembedded-core/2013-September/084159.html (From OE-Core rev: 3a66dd762e493ad2cda57110be67c3b06628050a) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Don't set DESCRIPTION to the same value as SUMMARYPaul Eggleton2013-12-0314-14/+0
| | | | | | | | | | | | Setting DESCRIPTION to the same value as SUMMARY doesn't do anything, since the value of DESCRIPTION will be derived from SUMMARY if not specified. (From OE-Core rev: e1e888585c84175580ad822d4a6c93f62e5ce16c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dropbear: set SUMMARY instead of DESCRIPTIONPaul Eggleton2013-12-031-1/+1
| | | | | | | | (From OE-Core rev: bd8fb95960cfbc9de4b796a4e5b22ef0b0dc1699) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eee-acpi-scripts: tidy up recipePaul Eggleton2013-12-031-7/+8
| | | | | | | | | | | | | * Set SUMMARY instead of DESCRIPTION * Move packaging variables to the end * Fix spacing in LICENSE assignment * Fix indenting (From OE-Core rev: 92f10f733a93f1772636603c0e910daf3eb9ff42) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-utils-alsaconf: tidy up path settingPaul Eggleton2013-12-031-2/+1
| | | | | | | | | | | * Set FILESEXTRAPATHS instead of FILESPATH * Don't set THISDIR, it's already set by base.bbclass (From OE-Core rev: e2bcf2c435cea196f1e9314ae6837aa4ab6b51ae) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* squashfs-tools: set SUMMARY instead of DESCRIPTIONPaul Eggleton2013-12-031-1/+1
| | | | | | | | | | Also tidy up value a little bit. (From OE-Core rev: a8e7efe23a5962610fb5818a9a802e737fca918f) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* squashfs-tools: drop FILESPATHPKGPaul Eggleton2013-12-031-3/+0
| | | | | | | | | | Drop FILESPATHPKG setting since it seems to be superfluous. (From OE-Core rev: 694d95c94d03fb1e63d6c52840a5149c3b166c2a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa: targetcontrol.py: add abstraction for running tests on different ↵Stefan Stanacar2013-12-031-0/+137
| | | | | | | | | | | | | | | | | | | | | | | | targets Add a new module which abstracts the target object used by testimage.bbclass The purpose of this module is to move the deployment of a target from testimage.bbclass, basically abstracting different implementations of how we setup a target and how it runs commands. It allows to select one implementation or another by setting TEST_TARGET (currently to: "qemu" and "simpleremote"). QemuTarget is used to start a qemu instance (as it's currently done in testimage.bbclass) SimpleRemoteTarget is meant for a remote machine (by setting TEST_TARGET_IP) that's already up and running with network and ssh. Simply put, it opens the door for running the tests on different types of targets by adding new classes (maybe qemu-nfsroot or remote-special etc.). One could also override BaseTarget which currently uses the existing SSHControl module and add a serial implementation. [ YOCTO #5554 ] (From OE-Core rev: c1bfd4017f6f6502a68ceb3edf7d2027d02a309d) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testimage: use the new targetcontrol.py module for running testsStefan Stanacar2013-12-037-116/+87
| | | | | | | | | | | | | | | | | | | | | | | | | | This patch makes the necessary changes for using the targetcontrol.py module so that one can run the same tests on a qemu instance or a remote machine based on the value of TEST_TARGET variable: "qemu" or "simpleremote". The default value is "qemu" which starts a qemu instance and it's the with what we currently have. With "simpleremote", the remote machine must be up with network and ssh and you need to set TEST_TARGET_IP with the IP address of the remote machine (it can still be a qemu instance that was manually started). Basically testimage.bbclass now does something along the lines of: - load tests -> deploy (prepare) / start target -> run tests. There were a couple of changes necessary for tests and also some cleanups/renames that were needed to adjust this change. (use ip everywhere when refering to target and server_ip when refering to host/build machine) Also two unnecessary and unsed methods were dropped from sshcontrol. [ YOCTO #5554 ] (From OE-Core rev: a7820350fa3271d78ed7476e02f4aef593be1125) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kmod: avoid parallel-testsTudor Florea2013-12-032-4/+7
| | | | | | | | | | | | buildtest-TESTS and runtest-TESTS targets are required by ptest. In order to have those targets in automake 1.13.4, serial-tests should be specified since parallel test is assumed by default and serial-tests is optional. (From OE-Core rev: b7a0e1c351e396af6470e59c428128789295bd96) Signed-off-by: Tudor Florea <tudor.florea@enea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: do not replace ccache in the middle of a pathYue Tao2013-12-031-1/+1
| | | | | | | | | | | | | Python recipe did a sed s/ccache/$(CCACHE) on the Makefile, which replaces all "ccache" including ones that consist of a full path. This leads to build error when building in a project path with "ccache" in its name. Fix it by only replacing "ccache " with "$(CCACHE) ". (From OE-Core rev: 1181112cf65bc0186807fc59399c5dddcb9f9449) Signed-off-by: Lei Liu <lei.liu2@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa: use the new manifest file for determining if a package is installedStefan Stanacar2013-12-031-10/+4
| | | | | | | | | | | | | | | | Use the new manifest file instead of ${WORKDIR}/installed_pkgs.txt for determining if an image has a certain package, because installed_pkgs.txt goes away with rm_work enabled. We can't use the IMAGE_MANIFEST var for the file path because that relies on IMAGE_NAME which changes at every run (because of date), so we use the link which points to the last one built. [ YOCTO #5072 ] (From OE-Core rev: f57c83fc33583c140f668946f3f3e79b960aa9ee) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa/selftest: add test modules for expected bitbake output and ↵Corneliu Stoicescu2013-12-032-0/+134
| | | | | | | | | | | | bitbake-layers Tests for bitbake-layers and expected output for some bitbake options. (From OE-Core rev: 8408a7700cd9cab4559ddae0bbe57f0d7fae5c37) Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa/selftest: buildoptions.py: add simple image build testsAlexandru Palalau2013-12-031-0/+86
| | | | | | | | | | | Build images and tests different build options like RM_OLD_IMAGE and for WARN_QA/ERROR_QA behaviour. (From OE-Core rev: 75d2a1a37a18a22b0da7ab5b30cf005c78bc313f) Signed-off-by: Alexandru Palalau <alexandrux.palalau@intel.com> Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-selftest: create a new test layer to be used by oe-selftest scriptCorneliu Stoicescu2013-12-0310-0/+98
| | | | | | | | | | | | | | Everything in this layer is meant to be used by tests called by scripts/oe-selftest. These are helper recipes/appends to test various bitbake options or scripts. Currently most of these files here only have "include test_recipe.inc" which is the file tests will actually use. (From OE-Core rev: 71a5053eea2aa0055663ccb2318eda866df49bb7) Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-selftest: script to run builds as unittest against bitbake or ↵Stefan Stanacar2013-12-035-0/+412
| | | | | | | | | | | | | | | | | | | | | | | | | | | | various scripts The purpose of oe-selftest is to run unittest modules added from meta/lib/oeqa/selftest, which are tests against bitbake tools. Right now the script it's useful for simple tests like: - "bitbake --someoption, change some metadata, bitbake X, check something" type scenarios (PR service, error output, etc) - or "bitbake-layers <...>" type scripts and yocto-bsp tools. This commit also adds some helper modules that the tests will use and a base class. Also, most of the tests will have a dependency on a meta-selftest layer which contains specially modified recipes/bbappends/include files for the purpose of the tests. The tests themselves will usually write to ".inc" files from the layer or in conf/selftest.inc (which is added as an include in local.conf at the start and removed at the end) It's a simple matter or sourcing the enviroment, adding the meta-selftest layer to bblayers.conf and running: oe-selftest to get some results. It would finish faster if at least a core-image-minimal was built before. [ YOCTO #4740 ] (From OE-Core rev: 41a4f8fb005328d3a631a9036ceb6dcf75754410) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/buildhistory: do git garbage collection after committingPaul Eggleton2013-12-031-0/+1
| | | | | | | | | | | | | | We don't normally perform any operations (such as "git pull") that trigger "git gc --auto", thus garbage collection never happens which means performance of accessing the repository degrades noticeably over time. Add an explicit "git gc --auto" to clean things up when needed. Thanks to Elijah Newren and Ross Burton for suggesting this. (From OE-Core rev: 4a45a999e0ad2e99581428a5a6d34f483c00544f) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/buildhistory: reduce parsing timePaul Eggleton2013-12-031-0/+6
| | | | | | | | | | | | | | Disable several python functions if not parsing within the worker context. This avoids executing expensive operations while parsing recipes (which is unnecessary). (Thanks to Richard Purdie for pointing out the issue and suggesting the workaround.) (From OE-Core rev: 540a2a30be21c3eca4323efbe91e7dcfc31a4c97) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/buildhistory: improve collection of package infoPaul Eggleton2013-12-031-43/+48
| | | | | | | | | | | | | | | | | | | | Use a function added to SSTATEPOSTINSTFUNCS and read the necessary information out of pkgdata, instead of using a function executed during do_package that reads the data directly. This has two benefits: * The package info collection will now work when the package content is restored from shared state * Adding/removing the inherit of buildhistory will no longer change the do_package signatures and force re-execution of that function for every recipe. Fixes [YOCTO #5358] (From OE-Core rev: cd7f7efcd5f297d876823b8f579ecefb9542b089) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/buildhistory: add additional variables to image informationPaul Eggleton2013-12-032-6/+6
| | | | | | | | | | Add PACKAGE_EXCLUDE and NO_RECOMMENDATIONS to the info we track for images, since these can change what ends up in the image. (From OE-Core rev: a10189366f180b87f5be20b66834b7e7a9bb8c12) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/buildhistory: drop cruft from old SRCREV tracking implementationPaul Eggleton2013-12-031-12/+0
| | | | | | | | | | | This should have been removed when the implementation was rewritten in OE-Core commit 2179db89436d719635f858c87d1e098696bead2a. The collected values weren't being used anywhere since then. (From OE-Core rev: cbc23a87c1897b7fda40f452dd36acb0bca3d197) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/package: write PE and PKGE out to pkgdataPaul Eggleton2013-12-031-0/+2
| | | | | | | | | | These are important parts of the version for every package, so we should include them in PKGDATA just as we include PV/PR/PKGV/PKGR. (From OE-Core rev: 5ceed97ba02a698f1c260c3f56cdf2cc156e6d8b) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/package: record PKGSIZE as total file size in pkgdataPaul Eggleton2013-12-032-10/+8
| | | | | | | | | | | | | | | | | | | | | We were using "du -sk" to collect the total size of all files in each package for writing out to PKGSIZE in each pkgdata file; however this reports the total space used on disk not the total size of all files, which means it is dependent on the block size and filesystem being used for TMPDIR on the build host. Instead, take the total of the size reported by lstat() for each packaged file, which we are already collecting for FILES_INFO in any case. Note: this changes PKGSIZE to be reported in bytes instead of kilobytes since this is what lstat reports, but this is really what we should be storing anyway so that we have the precision if we need it. Fixes [YOCTO #5334] (From OE-Core rev: 29615b36fca696822a715ece2afbe0bf9a43ed61) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/package: fix FILES_INFO serialisation in pkgdataPaul Eggleton2013-12-033-45/+21
| | | | | | | | | | | | | | | | | | | | | The FILES_INFO entry in each pkgdata file stores the list of files for each package. Make the following improvements to how this is stored: * Store paths as they would be seen on the target rather than erroneously including the full path to PKGDEST (which is specific to the build host the package was built on) * For simplicity when loading the data, store complete paths for each entry instead of trying to break off the first part and use it as the dict key * Record sizes for each file (as needed by Toaster) * Serialise the value explicitly using json rather than just passing it through str(). Fixes [YOCTO #5443]. (From OE-Core rev: ca86603607a69a17cc5540d69de0e242b33382d3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added the multilib* class.Scott Rifenbark2013-12-031-0/+16
| | | | | | | (From yocto-docs rev: df154cd0c0176c9d213ab03862b1fec41f94b4ec) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>