kumquat-buildroot/utils
Peter Korsgaard 4984d0f230 utils/add-custom-hashes: add script to manage global patch dir hashes
Add a script to manage the .hash files in the BR2_GLOBAL_PATCH_DIR for
packages using custom versions.

To use it, run in a configured Buildroot directory, E.G.

  make foo_defconfig; ./utils/add-custom-hashes

We support multiple patch directories in BR2_GLOBAL_PATCH_DIR.  If multiple
directories are specified then use the last one as that is likely to be the
most specific one.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
[Peter: silence command -v invocation]
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-11-12 11:59:27 +01:00
..
checkpackagelib utils/check-package: check ignored files exist 2023-05-13 12:08:25 +02:00
checksymbolslib boot/lpc32xxcdl: remove package 2023-08-10 19:41:42 +02:00
add-custom-hashes utils/add-custom-hashes: add script to manage global patch dir hashes 2023-11-12 11:59:27 +01:00
brmake
check-package utils/check-package: cleanup line reading 2023-09-02 17:47:48 +02:00
check-symbols
config utils/config: fix shellcheck errors 2023-02-08 15:28:30 +01:00
diffconfig
docker-run utils/docker-run: propagate user's proxy settings 2023-11-04 18:42:48 +01:00
genrandconfig utils/genrandconfig: add ubi handling 2023-08-12 22:06:21 +02:00
get-developers
getdeveloperlib.py utils/getdeveloperlib.py: handle file removal 2023-09-11 22:08:22 +02:00
readme.txt
scancpan
scanpypi
size-stats-compare
test-pkg utils/docker-run: fix shellcheck errors 2023-02-08 15:28:32 +01:00

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 of a package's Config.in and
    .mk files, and also tests them for various types of typoes.

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...)