kumquat-buildroot/utils
Thomas Petazzoni 3eb49f59d6 utils/genrandconfig: add missing new line when creating the configuration
When adding the custom BR2_WGET value in the configuration,
genrandconfig forgets to add a newline. Due to this, the next option
that is added is printed on the same line as BR2_WGET="", which causes
it to be ignored.

Due to this, in all builds, the line right after BR2_WGET was
ignored. It could have been BR2_ENABLE_DEBUG, BR2_INIT_BUSYBOX,
BR2_INIT_SYSTEMD, BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV,
BR2_STATIC_LIBS or BR2_PACKAGE_PYTHON_PY_ONLY depending on the
randomization.

Fix that by adding a proper newline at the end of the BR2_WGET option.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-11-18 08:37:11 +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 utils/config: new script to manipulate .config files on the command line 2017-09-27 22:45:35 +02:00
diffconfig utils/diffconfig: remove BR2_* prefix restriction 2018-10-21 19:57:06 +02:00
genrandconfig utils/genrandconfig: add missing new line when creating the configuration 2018-11-18 08:37:11 +01:00
get-developers utils/get-developers: make it callable from elsewhere than the toplevel directory 2018-10-20 17:24:13 +01:00
getdeveloperlib.py utils/get-developers: make it callable from elsewhere than the toplevel directory 2018-10-20 17:24:13 +01:00
readme.txt utils/readme.txt: add documentation of genrandconfig 2017-07-29 15:41:09 +02:00
scancpan utils/scancpan: print package/Config.in only when useful 2018-11-01 22:21:30 +01:00
scanpypi utils/scanpypi: use archive file name to specify the extraction folder 2018-11-02 21:35:08 +01:00
size-stats-compare size-stats-compare: fix code style 2018-03-13 22:27:19 +01:00
test-pkg utils/test-pkg: log the output of merge-config 2018-07-10 23:01:47 +02: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...)