summaryrefslogtreecommitdiffstats
path: root/scripts/bitbake-whatchanged
AgeCommit message (Collapse)Author
2023-10-19scripts/bitbake-whatchanged: removeAlexander Kanavin
This is not documented or tested, and indeed hasn't been producing useful reports for some time. The script works by redirecting STAMPS_DIR into a separate location, then running bitbake -S none, then comparing the two sets of stamp filenames with regexes: Match the stamp's filename group(1): PE_PV (may no PE) group(2): PR group(3): TASK group(4): HASH stamp_re = re.compile("(?P<pv>.*)-(?P<pr>r\d+)\.(?P<task>do_\w+)\.(?P<hash>[^\.]*)") Then there's some code that finds out what changed in the above between the two sets. Messing about with STAMPS_DIR like that isn't supported, and will either do nothing, or remove the original stamps. Also stamp filenames aren't really a 'public API'. For finding out the changes between two builds, 'bitbake -s printdiff' is a supported and tested option. It may be a bit too verbose, but that can be more easily fixed than rewriting bitbake-whatchanged into a working state. Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-08-12scripts: Add copyright statements to files without oneRichard Purdie
Where there isn't a copyright statement, add one to make it explicit. Also drop editor config lines where they were present and add license identifiers as MIT if there isn't one. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-03-14bitbake-whatchanged: change ending quote to proper periodRobert P. J. Day
Pretty sure that trailing quote should be a period; it appears to work properly. Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-05-09meta/lib+scripts: Convert to SPDX license headersRichard Purdie
This adds SPDX license headers in place of the wide assortment of things currently in our script headers. We default to GPL-2.0-only except for the oeqa code where it was clearly submitted and marked as MIT on the most part or some scripts which had the "or later" GPL versioning. The patch also drops other obsolete bits of file headers where they were encoountered such as editor modelines, obsolete maintainer information or the phrase "All rights reserved" which is now obsolete and not required in copyright headers (in this case its actually confusing for licensing as all rights were not reserved). More work is needed for OE-Core but this takes care of the bulk of the scripts and meta/lib directories. The top level LICENSE files are tweaked to match the new structure and the SPDX naming. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-02scripts: python3: change python to python3 in shebangEd Bartosh
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-02scripts: python3: get rid of __future__ importsEd Bartosh
Removed print_function and with_statement imports from __future__ as they're supported by python 3 by default. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-02scripts: python3: convert iterables to listsEd Bartosh
Converted return value of items() keys() and values() to lists when dictionary is modified in the loop and when the result is added to the list. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-22scripts/bitbake-whatchanged: migrate from optparse to argparseHumberto Ibarra
The script bitbake-whatchanged uses optparse library, which is deprecated since python 2.7. This migrates to argparse library. [Yocto #9634] Signed-off-by: Humberto Ibarra <humberto.ibarra.lopez@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-01-29bitbake-whatchanged: avoid double do_ task name prefixOlof Johansson
When used with --verbose, the heading for each task looks like === The verbose changes of example.do_do_compile: This should instead be === The verbose changes of example.do_compile: Signed-off-by: Olof Johansson <olof.johansson@axis.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-06-25scripts: consolidate code to find bitbake pathPaul Eggleton
Several of these scripts were using duplicated code (and slightly different methods) to find the path to bitbake and add its lib subdirectory to the Python import path. Add some common code to do this and change the scripts to use it. Fixes [YOCTO #5076]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2014-03-27scripts: Update after addtion of parameter to bitbake -SRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-07bitbake-whatchanged: print what is about to happenRobert Yang
* Contents: - Summary - Usage - Implementation summary - Output - TODO * Summary: This is used for printing what is about to happen between the current and last builds, for example: $ bitbake core-image-sato # Edit some recipes $ bitbake-whatchanged core-image-sato The changes will be printed. * Usage: bitbake-whatchanged [[opts] recipe] * Implementation summary: - Use the "STAMPS_DIR=<path> bitbake -S recipe" to generate the new stamps, compare these stamps to the one in the old stamps dir (tmp/stamps), so we will get what are changed. - When the "-v" (verbose) is not specified: > Figure out the newly added tasks > Figure out the PV (including PE) and PR changed tasks > The left tasks are the ones that the "Dependencies" changed tasks - When "-v" is specified: > Figure out the newly added tasks > Use bb.siggen.compare_sigfiles to figure out the details * Output, for example (core-image-sato with different git tags) and with recipes upgraded): - without "-v": Figuring out the STAMPS_DIR ... Generating the new stamps ... (need several minutes) === Newly added tasks: (5 tasks) core-image-sato: do_configure do_populate_lic do_install do_rootfs do_compile # Note: This is because the "bitbake -S" always generate the sigdata for # do_compile, do_rootfs and other task, we may need fix this from "bitbake -S" === PV changed: (130 tasks) alsa-utils: 1.0.25 -> 1.0.26 cross-localedef-native: 2.16 -> 2.17 eglibc-initial: 2.16 -> 2.17 [snip] === Dependencies changed: (3593 tasks) busybox: do_package do_package_write do_build do_packagedata do_populate_sysroot do_install do_compile do_package_write_rpm do_configure do_populate_lic atk-native: do_compile do_package_write_rpm do_package do_configure do_populate_sysroot do_install do_populate_lic do_patch do_packagedata do_build do_package_write do_unpack [snip] === Summary: (3728 changed, 1134 unchanged) Newly added: 5 PV changed: 130 PR changed: 0 Dependencies changed: 3593 Removing the newly generated stamps dir ... - with "-v": === Newly added tasks: (5 tasks) core-image-sato: do_configure do_populate_lic do_install do_rootfs do_compile === The verbose changes of glib-2.0-native.do_do_install: Hash for dependent task virtual:native:glib-2.0_2.34.3.bb.do_compile changed from bab8b8dd95be1b83dcec93f755b1812b to 70f746df7809acaa52de204b0685abb4 [snip] === Summary: (3728 changed, 1134 unchanged) Newly added: 5 Dependencies changed: 3723 Removing the newly generated stamps dir ... * TODO - It seems that the "bitbake -S core-image-sato" has bugs, it would always report errors, but doesn't fatal errors - The gcc-cross' stamps are in tmp/stamps/work-shared, but the "bitbake -S" doesn't put the stamps in work-shared. - The "bitbake -S" always generates the sigdata for image recipe's do_compile, do_install and other tasks, we may need fix this from "bitbake -S". - Print the ones which can be installed from the sstate. [YOCTO #1659] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>