Commit 56f21c28 authored by Arnout Vandecappelle's avatar Arnout Vandecappelle Committed by Thomas Petazzoni
Browse files

manual: update old references to support/scripts

There were still some references to the old location of the scripts in
the manual. Replace them by utils/.

While we're at it, remove the redundant ./ at the beginning of some of
the example commands.
Signed-off-by: default avatarArnout Vandecappelle (Essensium/Mind) <>
Cc: "Yann E. MORIN" <>
Acked-by: default avatar"Yann E. MORIN" <>
Signed-off-by: default avatarThomas Petazzoni <>
parent 27304521
......@@ -167,7 +167,7 @@ possible to customize what is done in any particular step:
If the Python package for which you would like to create a Buildroot
package is available on PyPI, you may want to use the +scanpypi+ tool
located in +support/scripts+ to automate the process.
located in +utils/+ to automate the process.
You can find the list of existing PyPI packages[here].
......@@ -178,7 +178,7 @@ your host.
When at the root of your buildroot directory just do :
./support/scripts/scanpypi foo bar -o package
utils/scanpypi foo bar -o package
This will generate packages +python-foo+ and +python-bar+ in the package
......@@ -198,7 +198,7 @@ If your Buildroot package is not in the official Buildroot tree but in
a br2-external tree, use the -o flag as follows:
./support/scripts/scanpypi foo bar -o other_package_dir
utils/scanpypi foo bar -o other_package_dir
This will generate packages +python-foo+ and +python-bar+ in the
......@@ -207,7 +207,7 @@ This will generate packages +python-foo+ and +python-bar+ in the
Option +-h+ will list the available options:
./support/scripts/scanpypi -h
utils/scanpypi -h
......@@ -326,7 +326,7 @@ Buildroot release, use the +size-stats-compare+ script. It takes two
Refer to the help text of this script for more details:
support/scripts/size-stats-compare -h
utils/size-stats-compare -h
......@@ -26,7 +26,7 @@ to include in his patch the appropriate modification to the
The +DEVELOPERS+ file format is documented in detail inside the file
The +get-developer+ tool, located in +support/scripts+ allows to use
The +get-developer+ tool, located in +utils/+ allows to use
the +DEVELOPERS+ file for various tasks:
- When passing one or several patches as command line argument,
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment