8f60241530
When dealing with enterprise-grade networks, it is more often than not the case that the wider internet is unreachable but through proxies. There is a usual set of variables that users can set in the environment to point various tools (curl, git...) to use those proxies. Propagate those variables inside the container. Note that there are a few tools (e.g. cvs, svn) that may not recognise those variables; instead, they require custom setup that is too complex to handle, so is left as an exercise to interested parties. Similarly, there are other types of proxy, socks4 or socks5, that also require custom setup that is not trivial to replicate in a container, so is also left out as an exercise for interested parties. In the large majority of cases, those few variables are enough to Make Things Work™. Signed-off-by: Yann E. MORIN <yann.morin@orange.com> Cc: Ricardo Martincoski <ricardo.martincoski@datacom.com.br> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> |
||
---|---|---|
.. | ||
checkpackagelib | ||
checksymbolslib | ||
brmake | ||
check-package | ||
check-symbols | ||
config | ||
diffconfig | ||
docker-run | ||
genrandconfig | ||
get-developers | ||
getdeveloperlib.py | ||
readme.txt | ||
scancpan | ||
scanpypi | ||
size-stats-compare | ||
test-pkg |
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-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...)