mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-06-02 13:29:49 +00:00
Code Issues Projects Releases Wiki Activity

manuals: define proper numbered lists

Browse Source 
Using "#." instead of "1.", "2.", "3.", etc.

(From yocto-docs rev: 11c2585acd0fa6c330702af2359ce5a9e47cde1f)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reported-by: Quentin Schulz <foss+yocto@0leil.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Michael Opdenacker
2022-12-09 19:01:55 +01:00
committed by Richard Purdie
parent 474e071608
commit 6846d4d00b
28 changed files with 347 additions and 347 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/sdk-manual/working-projects.rst
+11 -11
View File
@@ -31,7 +31,7 @@ project:
GNOME Developer
site.
1. *Create a Working Directory and Populate It:* Create a clean
#. *Create a Working Directory and Populate It:* Create a clean
directory for your project and then make that directory your working
location::
@@ -74,7 +74,7 @@ project:
bin_PROGRAMS = hello
hello_SOURCES = hello.c
2. *Source the Cross-Toolchain Environment Setup File:* As described
#. *Source the Cross-Toolchain Environment Setup File:* As described
earlier in the manual, installing the cross-toolchain creates a
cross-toolchain environment setup script in the directory that the
SDK was installed. Before you can use the tools to develop your
@@ -92,7 +92,7 @@ project:
$ source tmp/deploy/images/qemux86-64/environment-setup-core2-64-poky-linux
3. *Create the configure Script:* Use the ``autoreconf`` command to
#. *Create the configure Script:* Use the ``autoreconf`` command to
generate the ``configure`` script::
$ autoreconf
@@ -108,7 +108,7 @@ project:
which ensures missing auxiliary files are copied to the build
host.
4. *Cross-Compile the Project:* This command compiles the project using
#. *Cross-Compile the Project:* This command compiles the project using
the cross-compiler. The
:term:`CONFIGURE_FLAGS`
environment variable provides the minimal arguments for GNU
@@ -129,7 +129,7 @@ project:
$ ./configure --host=armv5te-poky-linux-gnueabi --with-libtool-sysroot=sysroot_dir
5. *Make and Install the Project:* These two commands generate and
#. *Make and Install the Project:* These two commands generate and
install the project into the destination directory::
$ make
@@ -149,7 +149,7 @@ project:
$ file ./tmp/usr/local/bin/hello
6. *Execute Your Project:* To execute the project, you would need to run
#. *Execute Your Project:* To execute the project, you would need to run
it on your target hardware. If your target hardware happens to be
your build host, you could run the project as follows::
@@ -227,7 +227,7 @@ established through the script::
To illustrate variable use, work through this simple "Hello World!"
example:
1. *Create a Working Directory and Populate It:* Create a clean
#. *Create a Working Directory and Populate It:* Create a clean
directory for your project and then make that directory your working
location::
@@ -266,7 +266,7 @@ example:
printf("\n");
}
2. *Source the Cross-Toolchain Environment Setup File:* As described
#. *Source the Cross-Toolchain Environment Setup File:* As described
earlier in the manual, installing the cross-toolchain creates a
cross-toolchain environment setup script in the directory that the
SDK was installed. Before you can use the tools to develop your
@@ -284,7 +284,7 @@ example:
$ source tmp/deploy/images/qemux86-64/environment-setup-core2-64-poky-linux
3. *Create the Makefile:* For this example, the Makefile contains
#. *Create the Makefile:* For this example, the Makefile contains
two lines that can be used to set the :term:`CC` variable. One line is
identical to the value that is set when you run the SDK environment
setup script, and the other line sets :term:`CC` to "gcc", the default
@@ -302,7 +302,7 @@ example:
rm -rf *.o
rm target_bin
4. *Make the Project:* Use the ``make`` command to create the binary
#. *Make the Project:* Use the ``make`` command to create the binary
output file. Because variables are commented out in the Makefile, the
value used for :term:`CC` is the value set when the SDK environment setup
file was run::
@@ -387,7 +387,7 @@ example:
use the SDK environment variables regardless of the values in the
Makefile.
5. *Execute Your Project:* To execute the project (i.e. ``target_bin``),
#. *Execute Your Project:* To execute the project (i.e. ``target_bin``),
use the following command::
$ ./target_bin