summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/migration.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2015-05-05 12:57:00 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-07-28 18:02:28 +0100
commitd9cf5753df7355b30309cc0640c2180eb3b38780 (patch)
treeb4e68ad8ab8c9f984b3ea0053bade45db9044d1f /documentation/ref-manual/migration.xml
parentfb82bcb989e20ea50fc683a66c39f343171d0d52 (diff)
downloadpoky-d9cf5753df7355b30309cc0640c2180eb3b38780.tar.gz
ref-manual: Added and updated variables to support calling functions
Fixed [YOCTO #7632] Looked for, updated, and added (if necessary) the following variables: * ROOTFS_PREPROCESS_COMMAND * ROOTFS_POSTPROCESS_COMMAND * SDK_POSTPROCESS_COMMAND * POPULATE_SDK_POST_TARGET_COMMAND * POPULATE_SDK_POST_HOST_COMMAND, * IMAGE_POSTPROCESS_COMMAND * IMAGE_PREPROCESS_COMMAND * ROOTFS_POSTUNINSTALL_COMMAND * ROOTFS_POSTINSTALL_COMMAND Each of these variables no longer accepts arbitrary shell commands but rather functions. The wordings now support that behavior. Also, updated the migration section for going to 1.6 release to note this change. (From yocto-docs rev: e1ab48f7def9d1eb080e007b88f75172470b8007) 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/migration.xml')
-rw-r--r--documentation/ref-manual/migration.xml29
1 files changed, 29 insertions, 0 deletions
diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml
index 7c78c9dd50..984485ede2 100644
--- a/documentation/ref-manual/migration.xml
+++ b/documentation/ref-manual/migration.xml
@@ -1413,6 +1413,35 @@
1413 it encounters the variable. 1413 it encounters the variable.
1414 </para> 1414 </para>
1415 </section> 1415 </section>
1416
1417 <section id='migration-1.6-variable-changes-variable-entry-behavior'>
1418 <title>Preprocess and Post Process Command Variable Behavior</title>
1419
1420 <para>
1421 The following variables now expect a semicolon separated
1422 list of functions to call and not arbitrary shell commands:
1423 <literallayout class='monospaced'>
1424 <link linkend='var-ROOTFS_PREPROCESS_COMMAND'>ROOTFS_PREPROCESS_COMMAND</link>
1425 <link linkend='var-ROOTFS_POSTPROCESS_COMMAND'>ROOTFS_POSTPROCESS_COMMAND</link>
1426 <link linkend='var-SDK_POSTPROCESS_COMMAND'>SDK_POSTPROCESS_COMMAND</link>
1427 <link linkend='var-POPULATE_SDK_POST_TARGET_COMMAND'>POPULATE_SDK_POST_TARGET_COMMAND</link>
1428 <link linkend='var-POPULATE_SDK_POST_HOST_COMMAND'>POPULATE_SDK_POST_HOST_COMMAND</link>
1429 <link linkend='var-IMAGE_POSTPROCESS_COMMAND'>IMAGE_POSTPROCESS_COMMAND</link>
1430 <link linkend='var-IMAGE_PREPROCESS_COMMAND'>IMAGE_PREPROCESS_COMMAND</link>
1431 <link linkend='var-ROOTFS_POSTUNINSTALL_COMMAND'>ROOTFS_POSTUNINSTALL_COMMAND</link>
1432 <link linkend='var-ROOTFS_POSTINSTALL_COMMAND'>ROOTFS_POSTINSTALL_COMMAND</link>
1433 </literallayout>
1434 For migration purposes, you can simply wrap shell commands in
1435 a shell function and then call the function.
1436 Here is an example:
1437 <literallayout class='monospaced'>
1438 my_postprocess_function() {
1439 echo "hello" > ${IMAGE_ROOTFS}/hello.txt
1440 }
1441 ROOTFS_POSTPROCESS_COMMAND += "my_postprocess_function; "
1442 </literallayout>
1443 </para>
1444 </section>
1416 </section> 1445 </section>
1417 1446
1418 <section id='migration-1.6-directory-layout-changes'> 1447 <section id='migration-1.6-directory-layout-changes'>