summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-01-02 16:20:45 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-01-08 13:02:03 +0000
commit3517a7651233f4d6a21432059adb037062048028 (patch)
tree88348d51824f2470e78f839b30348318a9dd3e54 /documentation/dev-manual
parent777601bb6e43ae66d48d6d63f83ccb5fe62e27bd (diff)
downloadpoky-3517a7651233f4d6a21432059adb037062048028.tar.gz
dev-manual: Edits to the "Post-Installation Scripts" section.
There was some confusion to this section as to just when post-install scripts were being executed. I looked it over and the section really is focusing more on the situations when you are creating a read-only root filesystem. So I went through and did a small amount of editing to just clean up some loose text. (From yocto-docs rev: 1b3674a5d123e74748bce5de61722079d4740908) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml24
1 files changed, 13 insertions, 11 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 3cb053c907..3e9cccef15 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -5436,8 +5436,8 @@
5436 sure all post-installation scripts succeed. 5436 sure all post-installation scripts succeed.
5437 If any of these scripts still need to be run after the root 5437 If any of these scripts still need to be run after the root
5438 filesystem is created, the build immediately fails. 5438 filesystem is created, the build immediately fails.
5439 These checks during build time ensure that the build fails 5439 These build-time checks ensure that the build fails
5440 rather than the target device fails later during its 5440 rather than the target device failing later during its
5441 initial boot operation. 5441 initial boot operation.
5442 </para> 5442 </para>
5443 5443
@@ -5447,7 +5447,7 @@
5447 so that they can run during root filesystem creation 5447 so that they can run during root filesystem creation
5448 (e.g. post-installation scripts for caching fonts). 5448 (e.g. post-installation scripts for caching fonts).
5449 However, if you create and add custom scripts, you need 5449 However, if you create and add custom scripts, you need
5450 to be sure they can be run during file system creation. 5450 to be sure they can be run during this file system creation.
5451 </para> 5451 </para>
5452 5452
5453 <para> 5453 <para>
@@ -5455,18 +5455,22 @@
5455 post-installation scripts from running during root filesystem 5455 post-installation scripts from running during root filesystem
5456 creation: 5456 creation:
5457 <itemizedlist> 5457 <itemizedlist>
5458 <listitem><para><emphasis>Not using $D in front of absolute paths:</emphasis> 5458 <listitem><para>
5459 <emphasis>Not using $D in front of absolute
5460 paths:</emphasis>
5459 The build system defines 5461 The build system defines
5460 <filename>$</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-D'><filename>D</filename></ulink> 5462 <filename>$</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-D'><filename>D</filename></ulink>
5461 at root filesystem creation time, and 5463 when the root filesystem is created.
5462 it is blank when run on the target device. 5464 Furthermore, <filename>$D</filename> is blank when the
5465 script is run on the target device.
5463 This implies two purposes for <filename>$D</filename>: 5466 This implies two purposes for <filename>$D</filename>:
5464 ensuring paths are valid in both the host and target 5467 ensuring paths are valid in both the host and target
5465 environments, and checking to determine which 5468 environments, and checking to determine which
5466 environment is being used as a method for taking 5469 environment is being used as a method for taking
5467 appropriate actions. 5470 appropriate actions.
5468 </para></listitem> 5471 </para></listitem>
5469 <listitem><para><emphasis>Attempting to run processes that are 5472 <listitem><para>
5473 <emphasis>Attempting to run processes that are
5470 specific to or dependent on the target 5474 specific to or dependent on the target
5471 architecture:</emphasis> 5475 architecture:</emphasis>
5472 You can work around these attempts by using native 5476 You can work around these attempts by using native
@@ -5475,10 +5479,8 @@
5475 which has the <filename>qemu_run_binary</filename> 5479 which has the <filename>qemu_run_binary</filename>
5476 function. 5480 function.
5477 For more information, see the 5481 For more information, see the
5478 <filename>meta/classes/qemu.bbclass</filename> 5482 <ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-qemu'><filename>qemu</filename></ulink>
5479 class in the 5483 class.</para></listitem>
5480 <link linkend='source-directory'>Source Directory</link>.
5481 </para></listitem>
5482 </itemizedlist> 5484 </itemizedlist>
5483 </para> 5485 </para>
5484 </section> 5486 </section>