diff options
Diffstat (limited to 'poky/documentation/overview-manual/concepts.rst')
| -rw-r--r-- | poky/documentation/overview-manual/concepts.rst | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/poky/documentation/overview-manual/concepts.rst b/poky/documentation/overview-manual/concepts.rst index d335c2fcdd..62f2327a7e 100644 --- a/poky/documentation/overview-manual/concepts.rst +++ b/poky/documentation/overview-manual/concepts.rst @@ -37,7 +37,7 @@ to each data source as a layer. For information on layers, see the ":ref:`dev-manual/layers:understanding and creating layers`" section of the Yocto Project Development Tasks Manual. -Following are some brief details on these core components. For +Here are some brief details on these core components. For additional information on how these components interact during a build, see the ":ref:`overview-manual/concepts:openembedded build system concepts`" @@ -1321,7 +1321,7 @@ can initialize the environment before using the tools. All the output files for an SDK are written to the ``deploy/sdk`` folder inside the :term:`Build Directory` as shown in the previous figure. Depending on the type of SDK, there are several variables to configure these files. -Here are the variables associated with an extensible SDK: +The variables associated with an extensible SDK are: - :term:`DEPLOY_DIR`: Points to the ``deploy`` directory. @@ -1375,7 +1375,7 @@ This next list, shows the variables associated with a standard SDK: Lists packages that make up the target part of the SDK (i.e. the part built for the target hardware). -- :term:`SDKPATH`: Defines the +- :term:`SDKPATHINSTALL`: Defines the default SDK installation path offered by the installation script. - :term:`SDK_HOST_MANIFEST`: @@ -2238,7 +2238,7 @@ which is integrating ``sayhello`` in our root file system: #. Add ``sayhello`` to :term:`IMAGE_INSTALL` to integrate it into the root file system -The following are the contents of ``libhello/Makefile``:: +The contents of ``libhello/Makefile`` are:: LIB=libhello.so @@ -2266,7 +2266,7 @@ The following are the contents of ``libhello/Makefile``:: and ``CFLAGS`` as BitBake will set them as environment variables according to your build configuration. -The following are the contents of ``libhello/hellolib.h``:: +The contents of ``libhello/hellolib.h`` are:: #ifndef HELLOLIB_H #define HELLOLIB_H @@ -2275,7 +2275,7 @@ The following are the contents of ``libhello/hellolib.h``:: #endif -The following are the contents of ``libhello/hellolib.c``:: +The contents of ``libhello/hellolib.c`` are:: #include <stdio.h> @@ -2283,7 +2283,7 @@ The following are the contents of ``libhello/hellolib.c``:: puts("Hello from a Yocto demo \n"); } -The following are the contents of ``sayhello/Makefile``:: +The contents of ``sayhello/Makefile`` are:: EXEC=sayhello LDFLAGS += -lhello @@ -2296,7 +2296,7 @@ The following are the contents of ``sayhello/Makefile``:: clean: rm -rf $(EXEC) *.o -The following are the contents of ``sayhello/sayhello.c``:: +The contents of ``sayhello/sayhello.c`` are:: #include <hellolib.h> @@ -2305,7 +2305,7 @@ The following are the contents of ``sayhello/sayhello.c``:: return 0; } -The following are the contents of ``libhello_0.1.bb``:: +The contents of ``libhello_0.1.bb`` are:: SUMMARY = "Hello demo library" DESCRIPTION = "Hello shared library used in Yocto demo" @@ -2328,7 +2328,7 @@ The following are the contents of ``libhello_0.1.bb``:: oe_soinstall ${PN}.so.${PV} ${D}${libdir} } -The following are the contents of ``sayhello_0.1.bb``:: +The contents of ``sayhello_0.1.bb`` are:: SUMMARY = "SayHello demo" DESCRIPTION = "SayHello project used in Yocto demo" |