buildroot/utils, branch 2017.11

perl: bump to version 5.26.1

2017-09-28T20:04:48+00:00

Signed-off-by: Francois Perrad Tested-by: Bernd Kuhls Signed-off-by: Peter Korsgaard

utils/config: new script to manipulate .config files on the command line

2017-09-27T20:45:35+00:00

Default prefix is set to `BR2_` but may be overidden by setting BR2_PREFIX. Example usage: Enable `BR2_PACKAGE_GNUPG`: ./utils/config --package --enable GNUPG Check state of config option `BR2_PACKAGE_GNUPG`: ./utils/config --package --state GNUPG y Enable `BR2_PACKAGE_GNUPG`: ./utils/config --package --disable GNUPG Set `BR2_TARGET_GENERIC_ISSUE` to "Welcome": ./utils/config --set-str TARGET_GENERIC_ISSUE "Welcome" Copied from the Linux kernel (4.13-rc6) source code and adapted to Buildroot. Thanks to Andi Kleen who is the original author of this script. Signed-off-by: Marcus Folkesson [Arnout: merge the two tr invications] Signed-off-by: Arnout Vandecappelle (Essensium/Mind)

scancpan: catch exception when MANIFEST is missing

2017-08-21T21:41:07+00:00

Signed-off-by: Francois Perrad Signed-off-by: Thomas Petazzoni

get-developers: add option to get developers for files

2017-08-14T20:39:57+00:00

The DEVELOPERS file lists file patterns, but the get-developers script only supports getting packages and CPU architectures. Some files are neither of those, e.g. defconfigs, support files, package infras, ... Add a '-f' option that allows to give a list of files for which to get the developer(s). Note that the DEVELOPERS file contains directories as well as files, and the directories are not expanded into individual files. Therefore, we have to use f.startswith(devfile) to match a directory. This assumes that the directory name ends with /, otherwise 'package/python' would also match 'package/python-foo'. Since we make sure that directories do end with / in the DEVELOPERS file, and since false positives are not much of an issue in this case, this isn't a problem. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

utils/readme.txt: add documentation of genrandconfig

2017-07-29T13:41:09+00:00

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

utils/test-pkg: add option to use an alternate toolchains CSV file

2017-07-29T13:40:55+00:00

When testing a package with test-pkg, it may be useful to override the set of toolchains used. For example: - to test with toolchains used in your company; - to test against a subset that is known to be problematic; - to use only toolchains you already have available locally when you have no network access. Add an option to use an alternate CSV file containing the config fragments of toolchains to try. Cc: "Yann E. MORIN" Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

test-pkg: use merge_config.sh to merge the fragments

2017-07-25T21:07:03+00:00

It is supposedly more robust than just concatenating. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Cc: Yann E. MORIN Signed-off-by: Thomas Petazzoni

genrandconfig: get configs from in-tree toolchain-configs.csv

2017-07-25T21:05:29+00:00

Now we have the toolchain config fragments in the buildroot directory itself, it is no longer necessary to fetch it from the toolchain URL. The --toolchains-url option is renamed to --toolchains-csv. The paths in the toolchains_csv file should be either absolute, or relative to buildrootdir. After this change, the script should be called from autobuild-run as: subprocess.call([os.path.join(srcdir, "utils/genrandconfig"), "-o", outputdir, "-b", srcdir, "--toolchains-csv", kwargs['toolchains_csv']], stdout=devnull, stderr=log) Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

test-pkg: get configs from in-tree toolchain-configs.csv

2017-07-25T21:03:28+00:00

Now we have the toolchain config fragments in the buildroot directory itself, it is no longer necessary to fetch it from the toolchain URL. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Cc: Yann E. MORIN Signed-off-by: Thomas Petazzoni

genrandconfig: use minimal.config

2017-07-25T21:01:08+00:00

This has a number of side-effects which must be handled. The lines in minimal.config may be overridden by the random lines added by amending the configuration, so is_toolchain_usable() shouldn't take those into account, or indeed the random lines added. Therefore, make a copy of the config before appending minimal.config and the random lines. While we're at it, rename the variable to the more appropriate toolchainconfig. minimal.config sets BR2_INIT_NONE=y, but we really also want to test with BR2_INIT_BUSYBOX=y. Therefore, add a random line to use the busybox init system. We set its probability rather high. The probabilities of systemd and eudev are increased since they're now in the else branch of BR2_INIT_BUSYBOX, which halves the probability that we even get there. We now also generate configurations without busybox. Previously, busybox was almost always selected due to BR2_INIT_BUSYBOX=y. Only if systemd is selected there was a chance to build without busybox. We now set BR2_SYSTEM_BIN_SH_NONE=y, the other /bin/sh options are never tested. However, this is not really something that is relevant to test in the autobuilders. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni