ccb4e5db5c
Currently, when we generate .checkpackageignore, we store, for each error, only the name of the function that generated that error. Although we currently do not have two check libs that have same-name check functions, there is nothing that would prevent that, and there is no reason why two unrelated libs could not implement checks with the same name. If such a situation were to arise, we'd have no way, when parsing the ignore list (in-tree: .checkpackageignore), to know which of the libs the exclusion would apply to. Fix that by storing both the library and function names together. The leading "checkpackagelib." (with the trailing dot, 16 chars) is removed for brevity, because it's present in all libs' names. As a consequence, regenerate .checkpackageignore. Note: people using that script to validate their br2-external trees will also have to regenerate their own exclusion list if they have one. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Ricardo Martincoski <ricardo.martincoski@datacom.com.br> Reviewed-by: Arnout Vandecappelle <arnout@mind.be> |
||
---|---|---|
.. | ||
checkpackagelib | ||
checksymbolslib | ||
add-custom-hashes | ||
brmake | ||
check-package | ||
check-symbols | ||
config | ||
diffconfig | ||
docker-run | ||
genrandconfig | ||
get-developers | ||
getdeveloperlib.py | ||
readme.txt | ||
scancpan | ||
scanpypi | ||
size-stats-compare | ||
test-pkg |
This directory contains various useful scripts and tools for working with Buildroot. You need not add this directory in your PATH to use any of those tools, but you may do so if you want. brmake a script that can be run instead of make, that prepends the date in front of each line, redirects all of the build output to a file ("'br.log' in the current directory), and just outputs the Buildroot messages (those lines starting with >>>) on stdout. Do not run this script for interactive configuration (e.g. menuconfig) or on an unconfigured directory. The output is redirected so you will see nothing. check-package a script that checks the coding style across the buildroot tree. It checks package's Config.in and .mk files, runs shellcheck for all shell scripts, flake8 for python files, checks for typoes, etc. It checks the .checkpackageignore file if errors should be ignored and errors if there's a file listed that doesn't produce an error. docker-run a script that runs a command (like make check-package) inside the buildroot CI docker container; pass no command to get an interactive shell. genrandconfig a script that generates a random configuration, used by the autobuilders (http://autobuild.buildroot.org). It selects a random toolchain from support/config-fragments/autobuild and randomly selects packages to build. get-developers a script to return the list of people interested in a specific part of Buildroot, so they can be Cc:ed on a mail. Accepts a patch as input, a package name or and architecture name. scancpan a script to create a Buildroot package by scanning a CPAN module description. scanpypi a script to create a Buildroot package by scanning a PyPI package description. size-stats-compare a script to compare the rootfs size between two different Buildroot configurations. This can be used to identify the size impact of a specific option, of a set of specific options, or of an update to a newer Buildroot version... test-pkg a script that tests a specific package against a set of various toolchains, with the goal to detect toolchain-related dependencies (wchar, threads...)