From 33e7953a5828a68d0468281a4e65df8092658a2b Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 21 Nov 2013 09:40:12 -0800 Subject: ref-manual: Cleaned up some instances of the term "working directory" This term should always reference a users current working directory and not be confused with the OpenEmbedded build system's "work directory (WORKDIR). I found several instances where the term "working directory" was not used correctly and fixed them. Reported-by: Robert P. J. Day (From yocto-docs rev: 80dcbf41fc57d0d527db13dd2f993233dd5c1675) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/technical-details.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'documentation/ref-manual/technical-details.xml') diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml index 6d4c6b712c..51b9148e3e 100644 --- a/documentation/ref-manual/technical-details.xml +++ b/documentation/ref-manual/technical-details.xml @@ -434,11 +434,11 @@ the checksum. First, there is the actual specific build path of a given task - the WORKDIR. - It does not matter if the working directory changes because it should not + It does not matter if the work directory changes because it should not affect the output for target packages. Also, the build process has the objective of making native or cross packages relocatable. The checksum therefore needs to exclude WORKDIR. - The simplistic approach for excluding the working directory is to set + The simplistic approach for excluding the work directory is to set WORKDIR to some fixed value and create the checksum for the "run" script. -- cgit v1.2.3-54-g00ecf