mirror/buildroot
1
0
Fork 0
mirror of https://gitlab.com/buildroot.org/buildroot.git synced 2026-08-08 00:20:38 -09:00
Code Issues Packages Projects Releases Wiki Activity

docs/manual: normalize delimiters of listing blocks

Browse Source 
Although the asciidoc toolchain accepts any number of ~ to delimit a
listing block (i.e. a code block), it is actually specified to be
exactly four, i.e. ~~~~. Currently, a mix of diffrent numbers of ~ are
being used - sometimes even a different number at the beginning and at
the end of the block.

Normalize this to always use exactly four ~ for the delimiter.

Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
This commit is contained in:
Arnout Vandecappelle
2024-07-12 20:23:24 +02:00
parent 4286c89f9d
commit 447fa1fca4
39 changed files with 298 additions and 298 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/manual/adding-packages-python.adoc
View File

@@ -15,7 +15,7 @@ system, generally recognizable by the usage of a +setup.py+ script or
First, let's see how to write a +.mk+ file for a Python package,
with an example :
------------------------
----
01: ################################################################################
02: #
03: # python-foo
@@ -32,7 +32,7 @@ with an example :
14: PYTHON_FOO_SETUP_TYPE = setuptools
15:
16: $(eval $(python-package))
------------------------
----
On line 7, we declare the version of the package.
@@ -170,9 +170,9 @@ your host.
When at the root of your buildroot directory just do :
-----------------------
----
utils/scanpypi foo bar -o package
-----------------------
----
This will generate packages +python-foo+ and +python-bar+ in the package
folder if they exist on https://pypi.python.org.
@@ -190,18 +190,18 @@ need to manually add the package to the +package/Config.in+ file.
If your Buildroot package is not in the official Buildroot tree but in
a br2-external tree, use the -o flag as follows:
-----------------------
----
utils/scanpypi foo bar -o other_package_dir
-----------------------
----
This will generate packages +python-foo+ and +python-bar+ in the
+other_package_directory+ instead of +package+.
Option +-h+ will list the available options:
-----------------------
----
utils/scanpypi -h
-----------------------
----
[[python-package-cffi-backend]]
@@ -219,17 +219,17 @@ Such a package should:
compiled C library wrapper on the target. This is achieved by adding
+select BR2_PACKAGE_PYTHON_CFFI+ to the package +Config.in+.
------------------------
----
config BR2_PACKAGE_PYTHON_FOO
bool "python-foo"
select BR2_PACKAGE_PYTHON_CFFI # runtime
------------------------
----
* add +host-python-cffi+ as a build-time dependency in order to
cross-compile the C wrapper. This is achieved by adding
+host-python-cffi+ to the +PYTHON_FOO_DEPENDENCIES+ variable.
------------------------
----
################################################################################
#
# python-foo
@@ -241,4 +241,4 @@ cross-compile the C wrapper. This is achieved by adding
PYTHON_FOO_DEPENDENCIES = host-python-cffi
$(eval $(python-package))
------------------------
----