summaryrefslogtreecommitdiff
path: root/meta/classes
AgeCommit message (Collapse)AuthorFiles
2011-05-11qmake_base.bbclass: add generate_qt_config_file taskOtavio Salvador1
This writes a qt.conf inside WORKDIR to properly configure projects based on CMake. This is required since qmake variables (returned by -query command) are fixed into the binary and can only be changed using a qt.conf file. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2011-05-11cmake.bbclass: fix qmake and rpath issuesOtavio Salvador2
Sync with OE at 3b7d83362027fde4f6850533ab83277d95dda961 however without changing the way of generating the toolchain file and making it branding agnostic. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2011-05-11siteinfo.bbclass: Add powerpc-linux-gnuspe.Leon Woestenberg1
Re-add powerpc-linux-gnuspe, from OpenEmbedded. Also adds support to poky.conf so that minimal-core-image builds with DISTRO=poky, [RP: Synced with recent diso file reoorg] Signed-off-by: Leon Woestenberg <leon@sidebranch.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-11metadata_scm.bbclass: Use COREBASE to grok for SCM operationsKhem Raj1
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2011-05-10insane.bbclass: skip license checksum if LICENSE is "CLOSED"Otavio Salvador1
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2011-05-10linux-yocto: error if meta data not presentBruce Ashfield1
There are valid reasons to build repositories without meta data present and there are times when this is an error. This change adds sanity tests to the build process to detect missing meta data and throw an informative error message. Sanity checking is only triggered from recipes (linux-yocto) that always require meta data to be present. Other recipes are not impacted and can auto-generate meta data as required. Without this change the build process suceeds, but incorrect meta data will be used (with no user knowledge), which is not the desired behaviour. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-05-10package_rpm: use target vendor informationAdrian Alonso1
* Instead of hardcoding target vendor string "-poky" use TARGET_VENDOR information in case of using external toolchains Signed-off-by: Adrian Alonso <aalonso@secretlab.ca>
2011-05-10image-mklibs: add microblaze arch supportAdrian Alonso1
* In function mklibs_optimize_image_doit * Add microblaze arch case for setting the dynamic_loader used by "mklibs" call Signed-off-by: Adrian Alonso <aalonso@secretlab.ca>
2011-05-10siteinfo: add microblaze target infoAdrian Alonso1
* Add microblaze target info * Microblaze soft CPU can be configured as big-endian/little-endian * Currently target info support for microblaze big endian, using prebuilt toolchains. Signed-off-by: Adrian Alonso <aalonso@secretlab.ca>
2011-05-10kernel-arch: add microblaze to valid archsAdrian Alonso1
* Add Microblaze target to valid arch list definition Signed-off-by: Adrian Alonso <aalonso@secretlab.ca>
2011-05-10insane: add micrblaze target infoAdrian Alonso1
* package_qa_get_machine_dict * Add microblaze dic entry for QA * Prebuilt toolchain triplet microblaze-unknown-linux-gnu- * TARGET_OS is linux-gnu for this toolchain Signed-off-by: Adrian Alonso <aalonso@secretlab.ca>
2011-05-08gettext.bbclass, bitbake.conf: Append nls options to EXTRA_OECONF instead of +=Khem Raj1
Some recipes do not defined EXTRA_OECONF in such cases += drops the --enable|--disable-nls options. In another case where recipe defines EXTRA_OECONF instead of adding/appending to it then --enable|--disable-nls options are lost from EXTRA_OECONF We define EXTRA_OECONF = "" in bitbake.conf so the variable exists always. We use _append instead of += so the option is added at very end and not lost. We only return empty gettext dependencies if its a target recipe in case when USE_NLS is not set because the native/cross/nativesdk recipes still need the gettext dependencies Signed-off-by: Khem Raj <raj.khem@gmail.com>
2011-05-08package.bbclass: convert unpackaged file message from 'info' to 'warn' so ↵Koen Kooi1
that it shows up on the console Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
2011-05-07sanity.bbclass: Add cpio to list of required utilities tested forRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-05boot-directdisk: fix bzImage source locationTom Zanussi1
Fixes yocto [BUGID #876] boot-directdisk.class looks in the wrong location for the bzImage to install. Make it look in the right place. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2011-05-05linux-yocto: safely process unbranched repositoriesBruce Ashfield1
The BSP bootstrap and -dev use cases can be applied against unbranched or repos without meta data. To allow the proper and safe processing of those repositories, slight modifications to the tools are required to pass the branch on the command line (rather than detecting it always) and to only checkout branches that exist. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-05-05linux-yocto: apply meta data to external reposBruce Ashfield1
To support quick uprev and testing, it is desireable to build repositories that do not have embedded meta data. In this scenario the meta data can be automatically created or provided externally. This commit supports the first situation by detecting the lack of meta data and then automatically creating a base set of meta files. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-05-04qemuimagetest: Enable toolchain automation tests in qemuimagetestJiajun Xu1
Enable toolchain automation tests in qemuimagetest framework. 3 C/C++ test projects are added to test toolchain - cvs, iptables and sudoku-savant. User needs to set TEST_SCEN to "toolchain" in local.conf to enable tests. Test case will check if toolchain tarball exists under "${DEPLOY_DIR}/sdk". And it will extract toolchain tarball into /opt. It requires user to chown /opt to non-root user, who will run qemuimagetest. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-05-04insane.bbclass: Checking for NLS too when checking gettext dependencyKhem Raj1
Checking for gettext is not needed when --disable-nls is used Let user know what variant of gettext is missing e.g. gettext-native, gettext-nativesdk etc, reveals a bit more for user Check for virtual/gettext Signed-off-by: Khem Raj <raj.khem@gmail.com>
2011-05-04logging: delete the oe(note|warn|fatal|debug) functionsDarren Hart1
The new logging.bbclass replaces the oe* logging functions with bb* equivalents. There are no longer any users of the oe* API within oe-core. Remove the oe* functions. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-05-04logging: update existing oe* logging users to the bb* interfaceDarren Hart10
The new bash logging class provides bbnote, bbwarn, bbfatal, and bbdebug replacements (as well as bbplain and bberror) for the oe* equivalents. Use the new bb* API in preparation to delete the oe* logging API. This patch was automatically generated by a sed script. The result has been visually inspected and used to build core-image-sato for qemux86. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-05-04gettext.bbclass: Updates to better handle gettext alternativesRichard Purdie2
* Change gettext dependency to virtual/gettext * Ensure INHIBIT_DEFAULT_DEPS removes gettext dependencies * Use BASEDEPENDS to ensure dependencies are added in native/nativesdk cases Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-04base.bbclass: Create a BASEDEPENDS variable other classes can use to add to ↵Richard Purdie1
the base dependencies, avoiding native/nativesdk issues Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-28autotools.bbclass: Copy gettext files only if --disable-nls is not setKhem Raj1
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2011-04-28insane.bbclass: Move code to add function to tasks toward the endKhem Raj1
Cosmetic change to make syntax highlighters happy Signed-off-by: Khem Raj <raj.khem@gmail.com>
2011-04-28logging: add bb* logging mechanisms for bash recipe functionsDarren Hart2
The following logging mechanisms are to be used in bash functions of recipes. They are intended to map one to one in intention and output format with the python recipe logging functions of a similar naming convention: bb.plain(), bb.note(), etc. For the time being, all of these print only to the task logs. Future enhancements may integrate these calls with the bitbake logging infrastructure, allowing for printing to the console as appropriate. The interface and intention statements reflect that future goal. Once it is in place, no changes will be necessary to recipes using these logging mechanisms. I opted to write new functions instead of modifying the oe* logging functions from base.bbclass (and utils.bbclass in oe) for a couple reasons. First, one of my goals was to generate a uniform logging API between bash and python in recipes. Second, there are no users of oe* logging in meta (oe-core) or meta-yocto, while several oe recipes do use them. I wanted to make a clean start with the freedom to change behavior without forcing the oe recipes to change or experience unexpected logging changes. Eventually, the oe recipes can be migrated to the new bb* logging routines and the existing oe* routines can be retired (deleted). Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Chris Larson <clarson@kergoth.com>
2011-04-28logging: fix oedebug loglevel testDarren Hart1
When the existing test for loglevel fails, the syntax used results in the recipe exiting with a silent failure. Performing any bash command after the test block resolves the problem, such as "shift" or "echo ''". Rewriting with 'if []; then' blocks provides a cleaner syntax and also resolves the failure. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-04-28sstate.bbclass: Reduce SSTATE_MANIFESTS assignment to be weakKhem Raj1
Distributions can then override this variable if needed useful e.g. when building uclibc/eglibc both using same tmpdir Signed-off-by: Khem Raj <raj.khem@gmail.com>
2011-04-22cpan.bbclass: export PERLHOSTLIB for perl modulesNitin A Kamble1
This makes sure that native perl .so can get loaded at the buildtime, and avoids following kind of errors while building perl modules: Nitin A Kamble <nitin.a.kamble@intel.com> 2011/04/20 + perl Makefile.PL EXPATLIBPATH=/disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib EXPATINCPATH=/disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/include *** Module name IN: /disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib/perl/5.12.2/Cwd.pm *** Module name OUT: /disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib/perl/5.12.2/Cwd.pm *** Module name IN: /disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib/perl/5.12.2/Fcntl.pm *** Module name OUT: /disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib/perl/5.12.2/Fcntl.pm Can't load '/disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib/perl/5.12.2/auto/Fcntl/Fcntl.so' for module Fcntl: /disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib/perl/5.12.2/auto/Fcntl/Fcntl.so: wrong ELF class: ELFCLASS32 at /disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib/perl/5.12.2/XSLoader.pm line 79. at /disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib/perl/5.12.2/Fcntl.pm line 215 BEGIN failed--compilation aborted at /disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib/perl/5.12.2/Fcntl.pm line 216. Compilation failed in require at /disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib/perl/5.12.2/File/Temp.pm line 146. BEGIN failed--compilation aborted at /disk0/pokybuild/build0/tmp/sysroots/qemux86/usr/lib/perl/5.12.2/File/Temp.pm line 146. Compilation failed in require at inc/Devel/CheckLib.pm line 12. BEGIN failed--compilation aborted at inc/Devel/CheckLib.pm line 12. Compilation failed in require at Makefile.PL line 5. BEGIN failed--compilation aborted at Makefile.PL line 5. ERROR: Function 'do_configure' failed (see /disk0/pokybuild/build0/tmp/work/i586-poky-linux/libxml-parser-perl-2.40-r0/temp/log.do_configure.16956 for further information) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2011-04-22Control over when package init scripts are runGary Thomas1
When a package is built, some installation scripts must be performed on the target. In the case of a complete image, these scripts are run by a separate step at init time, but only during the first boot (other package install scripts can just be run when the package is installed on the target). This patch lets the distribution (or user) decide when these postponed install scripts should run. The default is normally near the end of init, but there may be times when it's beneficial to run them earlier so the "when" can be overridden. Signed-off-by: Gary Thomas <gary@mlbassoc.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-04-21sanity.bbclass: Fixup Poky referencesRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-21Further cleanup of various poky referencesRichard Purdie3
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-21sanity.conf: Rename POKY_CONF_VERSION -> LOCALCONF_VERSION and make sanity ↵Richard Purdie1
versions weak assignment allowing the distro to override Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-20Rename poky-image.bbclass to core-image.bbclassRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
2011-04-20Rename poky-image-* -> core-image-* and task-poky-* -> task-core-*Richard Purdie2
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-20Replace POKYBASE with COREBASERichard Purdie4
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-20Remove obsolete scripts/classesRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-20Rename poky-init-build-env to oe-init-build-envRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-19kernel: Remove debug statementsDarren Hart1
A stray echo and du command from my development of the following patch remain in kernel.bbclass. Remove them. commit 3b49416fc7a7ee9bfe722f2e6089aa18df41dc58 Author: Darren Hart <dvhart@linux.intel.com> Date: Tue Mar 8 17:09:10 2011 -0800 kernel/bbclass: rework kernel and module classes to allow for building out-of-tree modules Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-19kernel: Copy over bzImage to sysroots during installDarren Hart1
Fixes [Yocto #987] The following commit introduced a build failure: Commit 3b49416fc7a7ee9bfe722f2e6089aa18df41dc58 Author: Darren Hart <dvhart@linux.intel.com> Date: Tue Mar 8 17:09:10 2011 -0800 kernel/bbclass: rework kernel and module classes to allow for building out-of-tree modules Resulting in: | install: cannot stat `/usr/local/test/intel-bsp/build/tmp/sysroots/n450/kernel/bzImage': No such file or directory | ERROR: Function 'build_boot_bin' failed (see /usr/local/test/intel-bsp/build/tmp/work/core2-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.1106 for further information) The bzImage file was not being copied to sysroot, correct that. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-18python-dir.bbclass: define default PYTHON_BASEVERSIONMartin Jansa1
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2011-04-12Allow JFFS2 image options to be overriddenGary Thomas1
Signed-off-by: Gary Thomas <gary@mlbassoc.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-04-12autotools: Pass --disable-silent-rules to configureColin Walters1
Non-verbose logs are really annoying when trying to debug a build failure. A lot of projects are copying in the flag to use AM_SILENT_RULES which automake gained recently. We need to undo this. We'll get a warning from configure if it's not recognized, but that's fine. Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-04-08sstate: ensure an ordered mapping between SSTATETASKS and SSTATETASKNAMESDexuan Cui1
Fix [YOCTO #964] A recent commit 25a6e5f9(sstate: use only unique set of SSTATETASK) breaks the ordered mapping between SSTATETASKS and SSTATETASKNAMES. As a result, in sstate_cleanall, the line taskname = tasks[namemap.index(name)] gets an incorrect result, and "bitbake -c cleanall" doesn't really remove the files populalted by do_populate_sysroot. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
2011-04-06distrodata.bbclass: Merge the get_pkg_info.log into checkpkg.csvMei Lei1
For easy view the check package result, merge the two files into checkpkg.csv, after that, the package report system will use checkpkg.csv instead of get_pkg_info.log. Signed-off-by: Mei Lei <lei.mei@intel.com>
2011-04-05image.bbclass: Disable ldconfig-native when using uclibcRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-05native, nativesdk, crosssdk: reset TARGET_FPUIlya Yanok3
When building one of the native, nativesdk or crosssdk packages TARGET_* variables' values are no longer related to the target we set via MACHINE variable, they are now related to the BUILD (native) or SDK (nativesdk, crosssdk) targets instead. We need to change TARGET_FPU variable accordingly or some of the recipes (the ones that check for TARGET_FPU value, most notably gcc and eglibc) might be confused. It's probably cleaner not to reset TARGET_FPU but to change it to something like ${BUILD_FPU} (for native) or ${SDK_FPU} (for crosssdk and nativesdk) but as long as BUILD and SDK are x86 it's safe to just reset TARGET_FPU. Signed-off-by: Ilya Yanok <yanok@emcraft.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-04image.bbclass: make execution ldconfig verboseNitin A Kamble1
The failure of ldconfig was not getting logged anywhere before. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>