From 89670c77ec8d1ab717666d31a544ad1c70cdb3f1 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 16 May 2018 15:00:47 -0700 Subject: dev-manual: Moved "Building Software from an External Source" section. This section is now organized under the parent "Building" section in the common tasks chapter. (From yocto-docs rev: bc1bc9965cda547e45ff09a1c9e77be5e8c0a3d9) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-common-tasks.xml | 150 ++++++++++----------- 1 file changed, 75 insertions(+), 75 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 6734b1f4b9..d4b99bc69f 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -6145,6 +6145,81 @@ + +
+ Building Software from an External Source + + + By default, the OpenEmbedded build system uses the + Build Directory + when building source code. + The build process involves fetching the source files, unpacking + them, and then patching them if necessary before the build takes + place. + + + + Situations exist where you might want to build software from source + files that are external to and thus outside of the + OpenEmbedded build system. + For example, suppose you have a project that includes a new BSP with + a heavily customized kernel. + And, you want to minimize exposing the build system to the + development team so that they can focus on their project and + maintain everyone's workflow as much as possible. + In this case, you want a kernel source directory on the development + machine where the development occurs. + You want the recipe's + SRC_URI + variable to point to the external directory and use it as is, not + copy it. + + + + To build from software that comes from an external source, all you + need to do is inherit the + externalsrc + class and then set the + EXTERNALSRC + variable to point to your external source code. + Here are the statements to put in your + local.conf file: + + INHERIT += "externalsrc" + EXTERNALSRC_pn-myrecipe = "path-to-your-source-tree" + + + + + This next example shows how to accomplish the same thing by setting + EXTERNALSRC in the recipe itself or in the + recipe's append file: + + EXTERNALSRC = "path" + EXTERNALSRC_BUILD = "path" + + + In order for these settings to take effect, you must globally + or locally inherit the + externalsrc + class. + + + + + By default, externalsrc.bbclass builds + the source code in a directory separate from the external source + directory as specified by + EXTERNALSRC. + If you need to have the source built in the same directory in + which it resides, or some other nominated directory, you can set + EXTERNALSRC_BUILD + to point to that directory: + + EXTERNALSRC_BUILD_pn-myrecipe = "path-to-your-source-tree" + + +
@@ -9992,81 +10067,6 @@ -
- Building Software from an External Source - - - By default, the OpenEmbedded build system uses the - Build Directory - when building source code. - The build process involves fetching the source files, unpacking - them, and then patching them if necessary before the build takes - place. - - - - Situations exist where you might want to build software from source - files that are external to and thus outside of the - OpenEmbedded build system. - For example, suppose you have a project that includes a new BSP with - a heavily customized kernel. - And, you want to minimize exposing the build system to the - development team so that they can focus on their project and - maintain everyone's workflow as much as possible. - In this case, you want a kernel source directory on the development - machine where the development occurs. - You want the recipe's - SRC_URI - variable to point to the external directory and use it as is, not - copy it. - - - - To build from software that comes from an external source, all you - need to do is inherit the - externalsrc - class and then set the - EXTERNALSRC - variable to point to your external source code. - Here are the statements to put in your - local.conf file: - - INHERIT += "externalsrc" - EXTERNALSRC_pn-myrecipe = "path-to-your-source-tree" - - - - - This next example shows how to accomplish the same thing by setting - EXTERNALSRC in the recipe itself or in the - recipe's append file: - - EXTERNALSRC = "path" - EXTERNALSRC_BUILD = "path" - - - In order for these settings to take effect, you must globally - or locally inherit the - externalsrc - class. - - - - - By default, externalsrc.bbclass builds - the source code in a directory separate from the external source - directory as specified by - EXTERNALSRC. - If you need to have the source built in the same directory in - which it resides, or some other nominated directory, you can set - EXTERNALSRC_BUILD - to point to that directory: - - EXTERNALSRC_BUILD_pn-myrecipe = "path-to-your-source-tree" - - -
-
Selecting an Initialization Manager -- cgit v1.2.3-54-g00ecf