summaryrefslogtreecommitdiffstats
path: root/meta/classes/base.bbclass
Commit message (Collapse)AuthorAgeFilesLines
* base.bbclass: check all entries of FILESPATH for MACHINE overridesJoshua Lock2012-02-221-6/+8
| | | | | | | | | | | | | | The logic which looks for MACHINE overrides in SRC_URI and updates PACKAGE_ARCH was checking only certain subdirectories of the recipes parent which, amongst other issues, doesn't account for SRC_URI overrides in layers. This patch changes the logic such that all FILESPATH entries are checked for children named for MACHINE. (From OE-Core rev: f2b572072c754048aaafdc4c42b71af87d61d9e7) Signed-off-by: Joshua Lock <josh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: replace COMMERCIAL_LICENSE code with LICENSE_FLAGS codeTom Zanussi2012-01-241-6/+6
| | | | | | | | | | | The COMMERCIAL_LICENSE mechanism has been superseded by LICENSE_FLAGS so remove the code that implements COMMERCIAL_LICENSE and replace it with the corresponding LICENSE_FLAGS version. (From OE-Core rev: 3735716996ec11691054d7f03db873afde89b143) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe: Add sstatesig, OE specific signature generator classesRichard Purdie2012-01-231-1/+1
| | | | | | | | | | | | | | | This patch adds SignatureGenerator classes specific to OE. For now, these emulate the previous behaviour with the exception that dependencies on quilt-native are now ignored for checksum purposes. The intent is to allow easier experimentation and customisation of this code in future as a result of these changes. Note that these changes require pending bitbake patches. (From OE-Core rev: cb73cf4299a192e6065d567fae700987c3f937aa) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/base: note variable name in COMPATIBLE_* skip messagesPaul Eggleton2012-01-171-2/+2
| | | | | | | | | | When raising SkipPackage for COMPATIBLE_MACHINE and COMPATIBLE_HOST exceptions, include the name of the variable as a hint to the user. (From OE-Core rev: c9f6fd20cf65799714b45a7bdfc3dd022b3d79cd) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* license.bbclass base.bbclass: support for 'or' operand in LICENSE and for ↵Andrei Gherzan2012-01-101-2/+1
| | | | | | | | | | | | | | | | | | SPDX license names A new function was defined in license.bbclass in order to correctly exclude packages where OE-Style licence naming is used. In this way licenses as GPL-3, GPLv3, GPLv3.0 etc will be excluded from a non-GPLv3 build. This function takes into consideration if 'or' operand is used. The function defined in license.bbclass is called in base.bbclass where packages are excluded based on INCOMPATIBLE_LICENSE variable. [YOCTO #1884] [YOCTO #1844] (From OE-Core rev: 28456593be0b7e15bb51595d547d7e5347cce24b) Signed-off-by: Andrei Gherzan <andrei at gherzan.ro> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Allow buildstats to be optionally suppliedMark Hatle2012-01-031-1/+0
| | | | | | | | | | | | | Buildstats should be allowed to be optionally enabled. It's recommended that it be enabled via the USER_CLASSES setting. Alternatively it could be enabled via the INHERIT_DISTRO or similar mechanism. (From OE-Core rev: 09b1dc8bd886c8cd2a5d4085d8bb4b73ece1f5b0) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add default PRINC 0 to be able to increment itMartin Jansa2011-12-051-1/+1
| | | | | | | (From OE-Core rev: 656793c706d84460f397b10ceb23ebb721ed3960) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/base: split out metadata revision code to separate functionPaul Eggleton2011-12-011-20/+24
| | | | | | | | | | | Split out a new function get_layers_branch_rev() which returns a list of the metadata layers and their revisions. This enables reuse in other places, such as buildhistory.bbclass. (From OE-Core rev: c1bca5d95051362320008f16d8f5acd87faa34ac) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* getVar/setVar cleanupsRichard Purdie2011-11-271-2/+2
| | | | | | | | | Complete the bb.data.getVar/setVar replacements with accesses directly to the data store object. (From OE-Core rev: 2864ff6a4b3c3f9b3bbb6d2597243cc5d3715939) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Use bb.plain to print the build headerRichard Purdie2011-11-241-1/+1
| | | | | | | | | If we just use print, the bitbake logging functions don't see the message and it can get lost if bitbake is for example logging messages to disk. (From OE-Core rev: 73a3d0d337e26c2be89c215efb8a2c3dd5d5994d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: add subversion-native to DEPENDS if there is svn:// in SRC_URIMartin Jansa2011-11-161-1/+7
| | | | | | | | | | | | * in some cases this could cause circual dependency (ie if we decide to apr_svn.bb or something like that before subversion-native in dependency tree), Saul said he had such case, but I wasn't able to reproduce it here (here it builds subversion-native-1.7.0 fine). (From OE-Core rev: 820bb7f4a0ced61ae62886bc7c5168151db919ea) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Convert to use direct access to the data store (instead of bb.data.*Var*())Richard Purdie2011-11-101-57/+57
| | | | | | | | | | | | | | | | | This is the result of running the following over the metadata: sed \ -e 's:bb.data.\(setVar([^,()]*,[^,()]*\), *\([^ )]*\) *):\2.\1):g' \ -e 's:bb.data.\(setVarFlag([^,()]*,[^,()]*,[^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^() ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -i `grep -ril bb.data *` (From OE-Core rev: b22831fd63164c4db9c0b72934d7d734a6585251) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Implement PACKAGECONFIGRichard Purdie2011-10-071-0/+38
| | | | | | | | | | | | | | | | | | These enabled options to be specified in the form: PACKAGECONFIG ?? = "<default options>" PACKAGECONFIG[foo] = "--enable-foo,--disable-foo,foo_depends,foo_runtime_depends" So that DEPENDS, RDEPENDS_${PN} and EXTRA_OECONF can be automatically built from specific options. Those options can easily be customised by the distro config or the user. Based on some ideas from Chris Elston <celston@katalix.com> but with an improved easier to use one line interface. (From OE-Core rev: 7a58911f6951abd56db9ebb37f8d6284d91fa514) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Minor cleanupRichard Purdie2011-10-071-5/+1
| | | | | | (From OE-Core rev: 373db49de0e30239fc8c7c3ce74d635fd7d6cd70) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Drop unneeded dependencyRichard Purdie2011-10-041-1/+1
| | | | | | | | | | | | | | | | patch depends on unpack configure depends on patch We simply don't need a configure dependency on unpack. This simplifies the dependencies of every recipe slightly and should make bitbake slightly faster at resovling dependency graphs. It also makes the .dot dependency graphs slightly more readable by removing noise. (From OE-Core rev: c54c1280fc0d06a53e23339c3913ec88eead13d9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Drop legacy code that is no longer useful/usedRichard Purdie2011-09-261-30/+0
| | | | | | | | | | | The code displaying console events has been handled by the bitbake UI since 1.8 so the legacy code path can be removed. If a log event is wanted, there are much better (and more complete) ways to do this so remove the EVENTLOG code too. (From OE-Core rev: aa60484384385a8b0f07e8062d58056a3670e399) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: add crosssdk items to INCOMPATIBLE_LICENSE exclude listSaul Wold2011-09-191-1/+1
| | | | | | | (From OE-Core rev: 1fbb665ef20b7a2477ec4812a610f2b69a870bb1) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: do not expand PREFERRED_PROVIDER for kernel recipeDongxiao Xu2011-09-131-1/+3
| | | | | | | | | | | | With Richard's commit f9c36392, we only build one kernel for a system, thus we shouldn't extend PREFERRED_PROVIDER for virtual/kernel. [YOCTO #1471] (From OE-Core rev: 90ad70fe13a9f8409387ca70289998bdca649aeb) Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: fix substring matching in COMMERCIAL_LICENSEPaul Eggleton2011-09-081-2/+2
| | | | | | | | | | | | | Previously, if for example you had a package called "mx", and a second package called "libomxil" listed in COMMERCIAL_LICENSE (without mx being listed there), it would match mx as being commercially licensed because mx is a substring of libomxil. Fix the search to ensure it only matches the listed package name exactly. (From OE-Core rev: b23e51e6c961cf3f7e2aaf89648fecce78424c99) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: clarify COMMERCIAL_LICENSE skip reasonPaul Eggleton2011-08-231-1/+1
| | | | | | | | | | | | | Change to a proper sentence and add a reference to the COMMERCIAL_LICENSE variable so that the user knows where this can be controlled. Addresses remainder of [YOCTO #846] (From OE-Core rev: 463d1719cc627ef22089282acfe70d7fcb835419) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Add MULTI_PROVIDER_WHITELIST manipulation for multilibRichard Purdie2011-08-101-0/+14
| | | | | | (From OE-Core rev: 4dbc340c63a86879fa727908cfb502f299f5d21b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Ensure PREFERRED_PROVIDER and PREFERRED_VERSION values are set ↵Richard Purdie2011-08-091-0/+45
| | | | | | | | for multilibs (From OE-Core rev: b12cd9f378eeafb6e23f379d5b005baa6e9a1a62) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base bbclass: add TUNE_FEATURES to the default bannerKoen Kooi2011-07-271-1/+1
| | | | | | | | | This makes debugging the new tune code easier since it doesn't involve staring at 'bitbake -e' output anymore. (From OE-Core rev: c1903b1221e9b419aefe49e40a8acd61575de797) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Fix PACKAGE_ARCH typoRichard Purdie2011-07-271-1/+1
| | | | | | (From OE-Core rev: 22a42df1843c8a95cf3be214a413d660adaadb32) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Add compatibility package name mapping handlerRichard Purdie2011-07-271-0/+8
| | | | | | | | | This means if PKGARCHCOMPAT_ARMV7A is set, "armv7a-vfp-neon" is renamed to be "armv7a". Other compatibility mappings can be added as needed. (From OE-Core rev: 08c0b7060009113e8dffdef51ff6b9b4b7f28894) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Fixed concurrency problem for ZIP packed recipes.Ihar Hrachyshka2011-07-201-0/+6
| | | | | | | | | | | | | | | The problem occured when unzip-native is not yet staged, and ZIP archive unpacking already started resulting in failed do_unpack task. (oe.dev has a NEED_UNZIP_FOR_UNPACK variable we did not bring over) [RP: Use srcuri from already existing variable] (From OE-Core rev: 6ca80453618fa308cc2d6329450aaf5dfdf2d610) Signed-off-by: Ihar Hrachyshka <ihar.hrachyshka@gmail.com> Signed-off-by: Koen Kooi <koen@openembedded.org> Signed-off-by: Tom Rini <tom_rini@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity, base: remove gcc3 check since qemu doesn't need it any morePhil Blundell2011-07-191-10/+0
| | | | | | | | | | | Recent versions of qemu seem to be happy enough building with gcc 4.x, and indeed most modern distributions aren't shipping gcc3 any more, so there is no point checking for its presence as part of sanity. Also remove the check_gcc3 function from base since nothing else uses it. (From OE-Core rev: ec5c68e9368111bd51c1cfd6a9a135c53b82ceca) Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: show layer's branches/revisions in the banner infoDexuan Cui2011-07-051-1/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The patch removes METADATA_BRANCH and METADATA_REVISION, and treats the meta/ in the same way as other layers. In the case some layers belonging to the same repo, the branch and revision are only printed once, but all the layer names are still printed. An example output can be: OE Build Configuration: BB_VERSION = "1.13.1" TARGET_ARCH = "i586" TARGET_OS = "linux" MACHINE = "emenlow" DISTRO = "poky" DISTRO_VERSION = "1.0+snapshot-20110702" TARGET_FPU = "" meta meta-yocto = "dcui/banner_v3:4b712dba68a98c827b8f3d0242da9153c4f65473" meta-emenlow meta-sugarbay meta-n450 = "dcui/test1:76d1178ba1a43cf6457c89717134aeb9f1275fae" (From OE-Core rev: f271498638a9da271ed5da973666fe4a7bd0ac63) Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ccache: Set CCACHE on a per recipe basisWenzong Fan2011-06-301-1/+1
| | | | | | | | | | | Set 'CCACHE_DIR' in 'bitbake.conf' and create the dirs for every package before task 'do_configure' started. [RP: Merge dirs variables into one] (From OE-Core rev: fe03f78fb0bf7d54b9472832e43764e882f918a1) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add umask task controlMark Hatle2011-06-301-0/+4
| | | | | | | | | | | | | | | | | | | | | | Bitbake now allows the umask to be specified per task. The following tasks will have a umask of 022 set by default: do_configure do_compile do_install do_package do_populate_sysroot do_rootfs do_configure and do_compile need a umask of 022 set because -many- recipes directly copy generated files out of recipe's build directory. Instead of fixing each existing and future recipe, it was shown to be much easier to just set the umask. (From OE-Core rev: 0cfa7ebcf661aa0645c6d4d858b04946ebacb7e4) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Back off the fatal error to a warning for now and try and recoverRichard Purdie2011-06-281-1/+2
| | | | | | (From OE-Core rev: 3a8e115904a227fcecb61e81f5e540d1aebea352) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base/glib-2.0: Simplify USE_NLS handling for glib-2.0Richard Purdie2011-06-281-4/+0
| | | | | | | | | | | | | | | Currently the only way to get anything to build is to set USE_NLS="yes" for glib-2.0. We might as well do this in the recipe by default for now and simpllify the code. The magic handling of USE_NLS_<recipename> is also removed since this can be done in the form USE_NLS_pn-<recipename> using overrides these days. (From OE-Core rev: 2e3727b05ae58aaf1eed88967c13cae085e7a702) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/conf: Drop MULTIMACH_ARCH variable, it adds unused complexity and ↵Richard Purdie2011-06-281-7/+1
| | | | | | | | | serves no useful purpose (From OE-Core rev: e623d3015bbdeb2b42b9763937be899a1fa9c0ca) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Since we require python 2.6 which always contains hashlib we ↵Richard Purdie2011-06-281-10/+0
| | | | | | | | | can drop this fallback code (From OE-Core rev: 4ac0b49b65106c2214ae80517fe9f66630d4540c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Drop old style SRCDATE handling, we have pn- overrides nowRichard Purdie2011-06-281-5/+0
| | | | | | | (From OE-Core rev: 0e88b873e758c158cde11009a8c6f9ca5f7a63dc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: add support for SOC_FAMILY in COMPATIBLE_MACHINESKoen Kooi2011-06-141-1/+3
| | | | | | | | | | | | | | | | * Add support for using SOC_FAMILY in the COMPATIBLE_MACHINES setting for a recipe. * This will allow recipes to work for entire families of devices without having to maintain/update the compatible devices as new devices are added into a family Based on 07076390358f211bd96779bec2d6eb5eaa0ad699 by Chase Maupin <chase.maupin@ti.com> (From OE-Core rev: dc303cbf25cf48aa98ff1979882820dd25f8cd9d) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* native/nativesdk: Clean up the depends ordering after bitbake override ↵Richard Purdie2011-06-091-2/+0
| | | | | | | | | | | | | | | handling updates This massively cleans up the dependency handling in the two classes when interacting with BBCLASSEXTEND. This change has a dependency on the bitbake override handling change and also the existence of the RecipePreFinalise event. (From OE-Core rev: f183c7cfe377fa6ed2777605c3590a9dda2060df) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: add cleansstate task between clean and cleanallMartin Jansa2011-06-061-2/+5
| | | | | | | | | * sometimes it's usefull to remove only sstate cache and keep downloaded sources for rebuild (From OE-Core rev: e071bc9982fc3ace3a32a990905884929392c4b6) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe.packagegroup: add code for package groups (sync from OE)Chris Larson2011-05-201-1/+1
| | | | | | | | | | | | | | | | This includes some utility functions for dealing with groups of packages defined in the metadata. Metadata syntax: PACKAGE_GROUP_<group> = "<list of packages>" If the packages in the group are optional: PACKAGE_GROUP_<group>[optional] = "1" (From OE-Core rev: 4df212e9c2a1dd7c80d180fd13b67e9f2799d3e1) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: use oe.data for OE_IMPORTS1.1_M1.rc1Chris Larson2011-05-201-1/+3
| | | | | | | (From OE-Core rev: e02c0d809732bed3d170880c6faedafce8c60c21) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Shift oe import logic out of the event handlerChris Larson2011-05-201-15/+18
| | | | | | | | | | This can be useful if we need the imports from another config parsed event handler, and can't rely upon the base one running before that one. (From OE-Core rev: dc579ce4dcf9a3743ced9eae4fe510a079961faf) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: switch to current OE's imports handlingChris Larson2011-05-201-13/+9
| | | | | | | | | | The current mechanism makes it easier for classes to add new oe modules to be automatically imported, and thereby made available to python snippets (${@}). (From OE-Core rev: 0c560a2a7954412f714db86b1aaadb7acbe72d1b) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Implement variable typing (sync from OE)Chris Larson2011-05-201-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This implementation consists of two components: - Type creation python modules, whose job it is to construct objects of the defined type for a given variable in the metadata - typecheck.bbclass, which iterates over all configuration variables with a type defined and uses oe.types to check the validity of the values This gives us a few benefits: - Automatic sanity checking of all configuration variables with a defined type - Avoid duplicating the "how do I make use of the value of this variable" logic between its users. For variables like PATH, this is simply a split(), for boolean variables, the duplication can result in confusing, or even mismatched semantics (is this 0/1, empty/nonempty, what?) - Make it easier to create a configuration UI, as the type information could be used to provide a better interface than a text edit box (e.g checkbox for 'boolean', dropdown for 'choice') This functionality is entirely opt-in right now. To enable the configuration variable type checking, simply INHERIT += "typecheck". Example of a failing type check: BAZ = "foo" BAZ[type] = "boolean" $ bitbake -p FATAL: BAZ: Invalid boolean value 'foo' $ Examples of leveraging oe.types in a python snippet: PACKAGES[type] = "list" python () { import oe.data for pkg in oe.data.typed_value("PACKAGES", d): bb.note("package: %s" % pkg) } LIBTOOL_HAS_SYSROOT = "yes" LIBTOOL_HAS_SYSROOT[type] = "boolean" python () { import oe.data assert(oe.data.typed_value("LIBTOOL_HAS_SYSROOT", d) == True) } (From OE-Core rev: a04ce490e933fc7534db33f635b025c25329c564) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Fix PR increment bug when PR number is a single digitKhem Raj2011-05-171-13/+6
| | | | | | | | | | | | | | | | PRINC which should add to base PR value has a problem when the PR is single digit e.g. r0 - r9. Current algorithm needed atleasts 2 digits to successfully populate end and begin markers. We reimplement the incrementing algorithm using regular expressions which addressed the above mentioned problem and simplifies the logic a bit and gets rid of loops and conditionals (From OE-Core rev: 9aeaae7b786a42d213ad4224743dfd49e2324077) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* logging: delete the oe(note|warn|fatal|debug) functionsDarren Hart2011-05-041-26/+1
| | | | | | | | | | | 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. (From OE-Core rev: 168d94be0e28fcbefda9df07d6d1b0cfd96e75fc) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* logging: update existing oe* logging users to the bb* interfaceDarren Hart2011-05-041-2/+2
| | | | | | | | | | | | | | 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. (From OE-Core rev: a1f09fce5caba389d0484b169f0cde85d64514fa) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Create a BASEDEPENDS variable other classes can use to add to ↵Richard Purdie2011-05-041-3/+5
| | | | | | | | the base dependencies, avoiding native/nativesdk issues (From OE-Core rev: fe2f1e1708e34758c70db37ce480453e10fc4eb1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* logging: add bb* logging mechanisms for bash recipe functionsDarren Hart2011-04-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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). (From OE-Core rev: 7cb3f0206619b725e404282fa7a3ac50b4609f1e) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* logging: fix oedebug loglevel testDarren Hart2011-04-281-4/+4
| | | | | | | | | | | | 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. (From OE-Core rev: 5857516404411040598b69c85d184ccdfc0af2e0) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base/kernel/image.bbclass: Clean up do_deploy ordering to ensure it just ↵Richard Purdie2011-03-291-0/+1
| | | | | | | | happens before a build completes (From OE-Core rev: a3b80688465ba5ba7e6d514f9a40ee224a9d3a28) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-16 11:36:55 +0000