summaryrefslogtreecommitdiff
path: root/meta/classes/utility-tasks.bbclass
AgeCommit message (Collapse)AuthorFiles
2016-12-16meta: remove True option to getVarFlag callsJoshua Lock1
getVarFlag() now defaults to expanding by default, thus remove the True option from getVarFlag() calls with a regex search and replace. Search made with the following regex: getVarFlag ?\(( ?[^,()]*, ?[^,()]*), True\) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-16meta: remove True option to getVar callsJoshua Lock1
getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?\(( ?[^,()]*), True\) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-10-03utility-tasks.bbclass: Use bb.fatal() instead of raising FuncFailedUlf Magnusson1
This sets a good example and avoids unnecessarily contributing to perceived complexity and cargo culting. Motivating quote below: < kergoth> the *original* intent was for the function/task to error via whatever appropriate means, bb.fatal, whatever, and funcfailed was what you'd catch if you were calling exec_func/exec_task. that is, it's what those functions raise, not what metadata functions should be raising < kergoth> it didn't end up being used that way < kergoth> but there's really never a reason to raise it yourself FuncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-21meta: Update to modern exception syntaxRichard Purdie1
Update older exception syntax to modern one required by python 3. Compatible with python 2.7. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-04classes/lib: Add expand parameter to getVarFlagRichard Purdie1
This sets the scene for removing the default False for expansion from getVarFlag. This would later allow True to become the default. On the most part this is an automatic translation with: sed -e 's:\(\.getVarFlag([^,()]*, [^,()]*\)):\1, True):g' -i `grep -ril getVar *` In this case, the default was False, but True was used since in most cases here expansion would be expected. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-29pth: DeleteKhem Raj1
replacement in npth is available in OE-core Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-06-23meta: Add explict getVar param for (non) expansionRichard Purdie1
Rather than just use d.getVar(X), use the more explict d.getVar(X, False) since at some point in the future, having the default of expansion would be nice. This is the first step towards that. This patch was mostly made using the command: sed -e 's:\(getVar([^,()]*\)\s*):\1, False):g' -i `grep -ril getVar *` Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-24classes/utility-tasks: make do_listtasks a little more friendlyPaul Eggleton1
* Sort the list so it's at least in some form of logical order. I looked at sorting by dependencies, but that's a topological sort, and given no such function is shipped as part of the python standard libraries it would seem excessive to pull one in just for this. In any case, I'm not sure that for the data we have this would lead to any particularly pleasing result. * Show the doc values as defined in documentation.conf (where present) as a description Addresses [YOCTO #4856]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-20utility-tasks/distrodata: Add recideptask flag for fetchall/checkuriallRichard Purdie1
See the bitbake commit adding the recideptask flag for details of the problem but in summary, we weren't seeing the [depends] of tasks like do_rootfs being taking into account for fetchall. This was leading to not all sources being fetched and this is the OE-Core part of the fix for this problem. BB_DEFAULT_TASK is the default task used since this is the one that most commands would end up targeting and is how users expect the command to behave. [YOCTO #4597] (From OE-Core rev: abf468963a087244887384122fd5202909e7f118) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-08-18utility-tasks: Set T to alternate location during do_cleanRichard Purdie1
There is a race where do_clean tries to clean WORKDIR but there are logfiles written into ${T} by bitbake and this can lead to exceptions due to open files. The easiest solution is to redirect T to a different location for the do_clean task, hence avoiding the errors and also allowing the logfiles to be visible somewhere. ${LOG_DIR} seems an appropriate place for this. [YOCTO #2846] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-19Convert tab indentation in python functions into four-spaceRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-04meta/classes: Update recrdeptask fields for recursive dependency handling ↵Richard Purdie1
changes in bitbake This also deletes the buildall task since I seen usecases for it. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-05meta: Replace bb.data.expand(xxx, d) -> d.expand(xxx)Richard Purdie1
sed \ -e 's:bb.data.\(expand([^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -i `grep -ril bb.data.expand *` Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-05meta: Convert getVar/getVarFlag(xxx, 1) -> (xxx, True)Richard Purdie1
Using "1" with getVar is bad coding style and "True" is preferred. This patch is a sed over the meta directory of the form: sed \ -e 's:\(\.getVar([^,()]*, \)1 *):\1True):g' \ -e 's:\(\.getVarFlag([^,()]*, [^,()]*, \)1 *):\1True):g' \ -i `grep -ril getVar *` Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-11-10Convert to use direct access to the data store (instead of bb.data.*Var*())Richard Purdie1
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 *` Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-03-01base/utility-tasks.bbclass: Drop do_setscene and do_rebuildRichard Purdie1
The do_setscene task only exists for rebuild support now as all its other functionality has been superceeded. The rebuild task currently crashes due to removal of the working directory and therefore isn't working for anyone. It also interacts extremely badly with the newer sstate technology to the point of being dangerous. Summary, if we want rebuild support it needs a reimplementation so remove this version and all its remnants and hacks. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-02-07utility-tasks: Update checkuri to new fetcher APIRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2010-11-28utility-tasks: Switch listtasks to use bb.plain() for printing outputRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-11-22utility-tasks.bbclass: Move distro related tasks to distrodata.bbclassDongxiao Xu1
Most of the d.keys() used in file parsing are variables in distro_tracking_fields.inc, which are not used in normal build. Therefore remove the inclusion of distro_tracking_fields.inc from poky.conf. Besides, move distro related tasks to distrodata.bbclass, which includes that tracking field file. By this change, the file parsing time could save about 25%. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2010-10-15distrodata: Modify Distro tracking spreadsheetSaul Wold1
Signed-off-by: Saul Wold <Saul.Wold@intel.com>
2010-09-02distro_check: fix for natives, cross, and initial recipe typesSaul Wold1
datetime checking is changed to be once per day Signed-off-by: Saul Wold <Saul.Wold@intel.com> distro_check: fix for natives, cross, and initial recipe types Signed-off-by: Saul Wold <Saul.Wold@intel.com>
2010-08-27sstate/utility-tasks: Ensure do_clean functions correctly and removes shared ↵Richard Purdie1
state Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-08-12utility-tasks.bbclass: Use python functions for do_clean instead of ↵Richard Purdie1
os.system, remove pointless [dirs] flag Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-27utility-tasks.bbclass: miscellaneous fixKevin Tian1
Fix parse error with packages such as spectrum-fw whose name has no version string. Later we may have per-recipe option to disable automatic check for those known with troubles, to reduce complexity in this part. Signed-off-by Kevin Tian <kevin.tian@intel.com>
2010-07-08utility-tasks.bbclass: add automatic version check for GIT/SVN protoKevin Tian1
both git/svn supports remote information query: 'git ls-remote', and 'svn info'. With them, now upstream version will be automatically checked for git/svn packages. In the meantime, manual latest version tagged in distro tracking fields are also compared as one alternative if upstream check fails. Also such check is one indicator whether tracking field is missing. Signed-off-by: Kevin Tian <kevin.tian@intel.com>
2010-06-03utility-tasks.bbclass: automatic upstream version checkKevin Tian1
Automatic upstream version check can be triggered by "bitbake xxx -c checkpkg". The rationale behind is to find a automatic way for version comparison between current in-use one and upstream progress. The tricky thing is how to find out useful version string from mass diverse information. Fortunately now it mostly work for wget based protocol, except some sites (e.g. sourceforge) not providing a directory service. Repo (git/svn/cvs) based protocols are handled in a very simple manner, by always tagging as update required. This will be further improved later. Use 'world' target to retrieve a full version check for all active recipes. Along with version check, other package information is also collected from existing fields in .bb file Signed-off-by Kevin Tian <kevin.tian@intel.com>
2010-06-02utility-tasks: Remove unneeded addtask parameterRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-06-02do_distro_check: Recipe exists in other distros?Nitin A Kamble1
This adds a new task (distro_check) for each recipe. The task generates the source package list for Fedora OpenSuSE Ubuntu Debian & Mandriva Linux distros. As one recipe or source package can generate multiple target packages the recipe name is compared with the source package name list of LInux distributions. Thread locking is used to avoid multiple threads racing for the package list update. Then the recipe name (PN) is checked if it exists in the package list of distros. And if the DISTRO_PN_ALIAS then it is used to copmare pacakge_name instead of the PN variable. Just for example the DISTRO_PN_ALIAS can be defined in the recipe (.bb) files like this In the file xset_1.0.4.bb: DISTRO_PN_ALIAS = "Fedora=xorg-x11-server-utils;\ Ubuntu=x11-xserver-utils; Debian=x11-xserver-utils;Opensuse=xorg-x11" The final results are stored in the tmp/log/distro_check-${DATETIME}.result file. FYI this command will generate the results for all recipies: bitbake world -f -c distro_check Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2010-03-22utility-tasks.bbclass: Remove unneeded base_ prefix since we don't EXPORT ↵Richard Purdie1
these functions any longer Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-19base.bbclass: Split up as per the patch in OE.dev by Chris Larson making ↵Richard Purdie1
code more readable and modularised Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-13 08:04:03 +0000