documentation: several manuals - Notes and links for filename space issue

Fixes [YOCTO_#3396]

Spaces in file and directory names is an issue for the build
system and throws an error when sourcing the environment
setup script.  I added key notes in several areas of the doc
set.  I also added some cross-references to the oe-init-build-env
section in some other areas where running the script is discussed.

(From yocto-docs rev: 1d102e91ba77391096749bd7df6c05b2b695b33f)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 16 insertions, 0 deletions

diff --git a/documentation/poky-ref-manual/ref-structure.xml b/documentation/poky-ref-manual/ref-structure.xml
index be2773b624..c2644df374 100644
--- a/documentation/poky-ref-manual/ref-structure.xml
+++ b/documentation/poky-ref-manual/ref-structure.xml
@@ -19,6 +19,13 @@
     section in the Yocto Project Development Manual.
 </para>
 
+<note>
+    The OpenEmbedded build system does not support file or directory names that
+    contain spaces.
+    Be sure that the Source Directory you use does not contain these types
+    of names.
+</note>
+
 <section id='structure-core'>
     <title>Top level core components</title>
 
@@ -177,6 +184,15 @@
             <literallayout class='monospaced'>
      $ source &OE_INIT_FILE; ~/mybuilds
             </literallayout>
+            <note>
+                The OpenEmbedded build system does not support file or directory names that
+                contain spaces.
+                If you attempt to run the <filename>&OE_INIT_FILE;</filename> script
+                from a Source Directory that contains spaces in either the filenames
+                or directory names, the script returns an error indicating no such 
+                file or directory.
+                Be sure to use a Source Directory free of names containing spaces.
+            </note>
         </para>
     </section>