buildroot/utils, branch 2017.08

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

genrandconfig: fix the case when outputdir is 'output'

2017-07-25T20:50:20+00:00

When outputdir is 'output' (the default), genrandconfig didn't work correctly because it expects the configfile in outputdir, while Buildroot puts it in the buildroot directory. Fix this by explicitly checking if outputdir == buildrootdir/output. Because abspath is used for both paths, string comparison works reliably. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

genrandconfig: calculate configfile only once

2017-07-25T20:50:07+00:00

The path to the .config file is calculated in several places - replace it with a single calculation, and pass configfile as an argument to is_toolchain_usable and fixup_config. These functions also don't need outputdir any more. This makes it easier to fix the case when configfile is not in outputdir. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

genrandconfig: pass outputdir and buildrootdir as arguments

2017-07-25T20:44:19+00:00

The --instance argument is just an artifact of genrandconfig's history as part of autobuild-run. It is much more logical to pass the output directory and the buildroot directory as arguments, with sane defaults. This also allows us to remove the hack of creating a symlink in the instance directory if it doesn't exist yet. Note that the default outputdir 'output' doesn't work yet, because in that case Buildroot will put the config file in the buildroot directory instead of the output directory. This will be fixed in a follow-up patch. 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-url", kwargs['toolchains_url']], stdout=devnull, stderr=log) Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

genrandconfig: calculate buildrootdir in main

2017-07-25T20:44:07+00:00

This prepares for passing buildrootdir as an argument. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni