kumquat-buildroot/utils
Peter Korsgaard 45aabcddc5 utils/get-developers: really make it callable from elsewhere than the toplevel directory
Commit 62d5558f76 (utils/get-developers: make it callable from elsewhere
than the toplevel directory) tried to fix this by passing in the toplevel
directory when the DEVELOPERS file is parsed.

Unfortunately this is not enough, as E.G.  also the paths listed in the
patches are relative to the toplevel directory, causing it to not match the
entries in the DEVELOPERS file.

In concept this can be fixed by also passing the toplevel directory to the
Developers class, but the simplest solution is just to chdir to the toplevel
Buildroot directory before calling any of the getdeveloperlib functions.

This does require us to finish parsing command line arguments (which opens
the provided patch files) to not get into trouble with relative paths to
patches before chdir'ing / initializing getdeveloperlib.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-01-04 13:23:41 +01:00
..
checkpackagelib utils/check-package: detect the use of ${} in .mk files 2018-09-21 00:05:55 +02:00
brmake
check-package check-package: support symlinks to the script 2018-04-01 22:41:54 +02:00
config
diffconfig utils/diffconfig: remove BR2_* prefix restriction 2018-10-21 19:57:06 +02:00
genrandconfig utils/genrandconfig: fix flake8 warnings 2018-12-03 22:25:42 +01:00
get-developers utils/get-developers: really make it callable from elsewhere than the toplevel directory 2019-01-04 13:23:41 +01:00
getdeveloperlib.py Revert "utils/get-developers: make it callable from elsewhere than the toplevel directory" 2019-01-04 13:23:33 +01:00
readme.txt
scancpan utils/scancpan: allow the generation of more tests 2018-12-06 22:20:10 +01:00
scanpypi utils/scanpypi: write _SOURCE only when needed 2018-12-30 17:42:32 +01:00
size-stats-compare
test-pkg utils/test-pkg: force checking dependencies 2019-01-03 11:41:26 +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-developpers
    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...)