summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/faq.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual/faq.xml')
-rw-r--r--documentation/ref-manual/faq.xml6
1 files changed, 4 insertions, 2 deletions
diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml
index 71fb03aedb..69b679bbf7 100644
--- a/documentation/ref-manual/faq.xml
+++ b/documentation/ref-manual/faq.xml
@@ -682,9 +682,11 @@
682 <para> 682 <para>
683 Yes - you can easily do this. 683 Yes - you can easily do this.
684 When you use BitBake to build an image, all the build output 684 When you use BitBake to build an image, all the build output
685 goes into the directory created when you source the 685 goes into the directory created when you run the
686 build environment setup script (i.e.
686 <link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link> 687 <link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link>
687 setup script. 688 or
689 <link linkend='structure-memres-core-script'><filename>oe-init-build-env-memres</filename></link>).
688 By default, this <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> 690 By default, this <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
689 is named <filename>build</filename> but can be named 691 is named <filename>build</filename> but can be named
690 anything you want. 692 anything you want.