diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-06-02 15:22:28 +0300 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-06-18 10:30:43 +0100 |
commit | 84ee8c653a45ffbda1fd3773f5fbb67d20d1bfc3 (patch) | |
tree | 1d1a761a861ee95f583666ff8382fd7dda7dcdd1 /documentation/ref-manual/ref-structure.xml | |
parent | fae1d7d56779ecf662ff04541abe431ca669940e (diff) | |
download | poky-84ee8c653a45ffbda1fd3773f5fbb67d20d1bfc3.tar.gz |
ref-manual, dev-manual: Updates for custom template configuration directory.
Fixes [YOCTO #5895]
I created a new section in the dev-manual titles
"Creating a Custom Template Configuration Directory" that describes
how the build system uses the template local.conf and bblayers.conf
and conf-notes.txt files as a basis when creating the real
deals in the build directory's conf folder. The context of this
is so that the user can create their own directory with their own
template files for repeated configurations and to create a custom
conf-notes.txt file should they want the setup scripts to display
some custom list of targets.
I also modified the two script references in the ref-manual for
oe-init-build-env and oe-init-build-env-memres. I needed to
link to the "how-to" section and added a bit in there about how
the scripts go about forming the conf files in the build directory.
(From yocto-docs rev: c07fb7082fe08387bbc546b2a23620dedc7127b8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/ref-structure.xml')
-rw-r--r-- | documentation/ref-manual/ref-structure.xml | 28 |
1 files changed, 24 insertions, 4 deletions
diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml index 1549d90357..c849dbda33 100644 --- a/documentation/ref-manual/ref-structure.xml +++ b/documentation/ref-manual/ref-structure.xml | |||
@@ -240,8 +240,10 @@ | |||
240 | Should you have custom distributions, it is very easy to modify | 240 | Should you have custom distributions, it is very easy to modify |
241 | this configuration file to include your targets for your | 241 | this configuration file to include your targets for your |
242 | distribution. | 242 | distribution. |
243 | Simply edit the list within the file and when you run the | 243 | See the |
244 | environment setup script you see your customized list of targets. | 244 | "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-a-custom-template-configuration-directory'>Creating a Custom Template Configuration Directory</ulink>" |
245 | section in the Yocto Project Development Manual for more | ||
246 | information. | ||
245 | </para> | 247 | </para> |
246 | 248 | ||
247 | <para> | 249 | <para> |
@@ -258,6 +260,14 @@ | |||
258 | <literallayout class='monospaced'> | 260 | <literallayout class='monospaced'> |
259 | $ source &OE_INIT_FILE; ~/mybuilds | 261 | $ source &OE_INIT_FILE; ~/mybuilds |
260 | </literallayout> | 262 | </literallayout> |
263 | The OpenEmbedded build system uses the template configuration | ||
264 | files, which are found by default in the | ||
265 | <filename>meta-yocto/conf</filename> directory in the | ||
266 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. | ||
267 | See the | ||
268 | "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-a-custom-template-configuration-directory'>Creating a Custom Template Configuration Directory</ulink>" | ||
269 | section in the Yocto Project Development Manual for more | ||
270 | information. | ||
261 | <note> | 271 | <note> |
262 | The OpenEmbedded build system does not support file or directory names that | 272 | The OpenEmbedded build system does not support file or directory names that |
263 | contain spaces. | 273 | contain spaces. |
@@ -349,8 +359,10 @@ | |||
349 | Should you have custom distributions, it is very easy to modify | 359 | Should you have custom distributions, it is very easy to modify |
350 | this configuration file to include your targets for your | 360 | this configuration file to include your targets for your |
351 | distribution. | 361 | distribution. |
352 | Simply edit the list within the file and when you run the | 362 | See the |
353 | environment setup script you see your customized list of targets. | 363 | "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-a-custom-template-configuration-directory'>Creating a Custom Template Configuration Directory</ulink>" |
364 | section in the Yocto Project Development Manual for more | ||
365 | information. | ||
354 | </para> | 366 | </para> |
355 | 367 | ||
356 | <para> | 368 | <para> |
@@ -368,6 +380,14 @@ | |||
368 | <literallayout class='monospaced'> | 380 | <literallayout class='monospaced'> |
369 | $ source oe-init-build-env-memres ~/mybuilds | 381 | $ source oe-init-build-env-memres ~/mybuilds |
370 | </literallayout> | 382 | </literallayout> |
383 | The OpenEmbedded build system uses the template configuration | ||
384 | files, which are found by default in the | ||
385 | <filename>meta-yocto/conf</filename> directory in the | ||
386 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. | ||
387 | See the | ||
388 | "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-a-custom-template-configuration-directory'>Creating a Custom Template Configuration Directory</ulink>" | ||
389 | section in the Yocto Project Development Manual for more | ||
390 | information. | ||
371 | <note> | 391 | <note> |
372 | The OpenEmbedded build system does not support file or | 392 | The OpenEmbedded build system does not support file or |
373 | directory names that contain spaces. | 393 | directory names that contain spaces. |