mirror of
https://git.busybox.net/buildroot.git
synced 2024-11-23 05:23:39 +08:00
8aad67f157
At the moment, it is difficult to combine brmake with docker-run. `docker-run brmake ...` doesn't work because our docker image doesn't have unbuffer. In addition, inside the container the timezone is UTC, but you probably want the timestamps added by brmake to be in local time. Therefore, it's better to have the call to docker-run nested inside brmake. Currently, brmake doesn't have any way to pass parameters, all of "$@" is passed unchanged to the `make` invocation. Thus, there is no established way to pass in the option whether or not to use docker. We choose to use an environment variable to pass in the option. The convention is that such a buildroot-specific environment variable should start with BR2_, so we choose BR2_DOCKER. Run make inside docker-run if the BR2_DOCKER environment variable is set. Update utils/readme.txt (the only existing documentation of brmake) with this information. Signed-off-by: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
57 lines
2.3 KiB
Plaintext
57 lines
2.3 KiB
Plaintext
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.
|
|
To run this within a container using docker-run (see below), set
|
|
BR2_DOCKER=y in the environment, i.e. call it as
|
|
`BR2_DOCKER=y utils/brmake`.
|
|
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 across the buildroot tree. It
|
|
checks package's Config.in and .mk files, runs shellcheck for all shell
|
|
scripts, flake8 for python files, checks for typos, etc.
|
|
It checks the .checkpackageignore file if errors should be ignored and
|
|
errors if there's a file listed that doesn't produce an error.
|
|
|
|
docker-run
|
|
a script that runs a command (like make check-package) inside the
|
|
buildroot CI docker container; pass no command to get an interactive
|
|
shell.
|
|
|
|
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...)
|