jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-07-27 21:26:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

manual: update old references to support/scripts

Browse Source 
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: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
Arnout Vandecappelle 2017-07-01 18:40:40 +02:00 committed by Thomas Petazzoni
parent 2730452176
commit 56f21c283c
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/manual/adding-packages-python.txt
View File

@ -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 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 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 You can find the list of existing PyPI packages
https://pypi.python.org[here]. https://pypi.python.org[here].
@ -178,7 +178,7 @@ your host.
When at the root of your buildroot directory just do : 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 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: 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 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: Option +-h+ will list the available options:
----------------------- -----------------------
./support/scripts/scanpypi -h utils/scanpypi -h
----------------------- -----------------------
[[python-package-cffi-backend]] [[python-package-cffi-backend]]

2
docs/manual/common-usage.txt
View File

@ -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: Refer to the help text of this script for more details:
---------------- ----------------
support/scripts/size-stats-compare -h utils/size-stats-compare -h
---------------- ----------------
include::eclipse-integration.txt[] include::eclipse-integration.txt[]

2
docs/manual/developers.txt
View File

@ -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 +DEVELOPERS+ file format is documented in detail inside the file
itself. itself.
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: the +DEVELOPERS+ file for various tasks:
- When passing one or several patches as command line argument, - When passing one or several patches as command line argument,