diff options
| author | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2017-07-01 18:07:00 +0200 |
|---|---|---|
| committer | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2017-07-01 18:07:00 +0200 |
| commit | 7ca9fc3170de1a41fbcbc5dfdc2838c75bff72a5 (patch) | |
| tree | 414aac66ba7b23b1f9e4beca5fa02bd83dd90202 /docs | |
| parent | afdb545b2847d2a922ee202775998d4658900fec (diff) | |
| download | buildroot-7ca9fc3170de1a41fbcbc5dfdc2838c75bff72a5.tar.gz buildroot-7ca9fc3170de1a41fbcbc5dfdc2838c75bff72a5.zip | |
tools: rename to 'utils'
After some discussion, we found out that "tools" has the four first
letters identical to the "toolchain" subfolder, which makes it a bit
unpractical with tab-completion. So, this commit renames "tools" to
"utils", which is more tab-completion-friendly.
This has been discussed with Arnout and Yann.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/manual/adding-packages-tips.txt | 8 | ||||
| -rw-r--r-- | docs/manual/contribute.txt | 2 | ||||
| -rw-r--r-- | docs/manual/writing-rules.txt | 2 |
3 files changed, 6 insertions, 6 deletions
diff --git a/docs/manual/adding-packages-tips.txt b/docs/manual/adding-packages-tips.txt index 0047dfd14f..8b2361d20d 100644 --- a/docs/manual/adding-packages-tips.txt +++ b/docs/manual/adding-packages-tips.txt @@ -45,7 +45,7 @@ continuously test random configurations. However, these only build the `master` branch of the git tree, and your new fancy package is not yet there. -Buildroot provides a script in +tools/test-pkg+ that uses the same base +Buildroot provides a script in +utils/test-pkg+ that uses the same base configurations as used by the autobuilders so you can test your package in the same conditions. @@ -74,7 +74,7 @@ Then run the +test-pkg+ script, by telling it what config snippet to use and what package to test: ---- -$ ./tools/test-pkg -c libcurl.config -p libcurl +$ ./utils/test-pkg -c libcurl.config -p libcurl ---- This will try to build your package against all the toolchains used @@ -83,7 +83,7 @@ too long to do so). The output lists all toolchains and the corresponding result (excerpt, results are fake): ---- -$ ./tools/test-pkg -c libcurl.config -p libcurl +$ ./utils/test-pkg -c libcurl.config -p libcurl armv5-ctng-linux-gnueabi [ 1/11]: OK armv7-ctng-linux-gnueabihf [ 2/11]: OK br-aarch64-glibc [ 3/11]: SKIPPED @@ -124,7 +124,7 @@ The +test-pkg+ script accepts a few options, for which you can get some help by running: ---- -$ ./tools/test-pkg -h +$ ./utils/test-pkg -h ---- [[github-download-url]] diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt index c10587726c..a58945f395 100644 --- a/docs/manual/contribute.txt +++ b/docs/manual/contribute.txt @@ -295,7 +295,7 @@ information). This tool reads your patches and outputs the appropriate +git send-email+ command to use: --------------------- -$ ./tools/get-developers outgoing/* +$ ./utils/get-developers outgoing/* --------------------- Use the output of +get-developers+ to send your patches: diff --git a/docs/manual/writing-rules.txt b/docs/manual/writing-rules.txt index c144874a0d..ca43272287 100644 --- a/docs/manual/writing-rules.txt +++ b/docs/manual/writing-rules.txt @@ -146,6 +146,6 @@ syntax, refer to http://www.methods.co.nz/asciidoc/userguide.html[]. === Support scripts -Some scripts in the +support/+ and +tools/+ directories are written in +Some scripts in the +support/+ and +utils/+ directories are written in Python and should follow the https://www.python.org/dev/peps/pep-0008/[PEP8 Style Guide for Python Code]. |
