summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/faq.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual/faq.rst')
-rw-r--r--documentation/ref-manual/faq.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst
index 3eee9e1be5..2fcbf7da96 100644
--- a/documentation/ref-manual/faq.rst
+++ b/documentation/ref-manual/faq.rst
@@ -364,7 +364,7 @@ redirect requests through proxy servers.
364 364
365**Q:** Can I get rid of build output so I can start over? 365**Q:** Can I get rid of build output so I can start over?
366 366
367**A:** Yes - you can easily do this. When you use BitBake to build an 367**A:** Yes --- you can easily do this. When you use BitBake to build an
368image, all the build output goes into the directory created when you run 368image, all the build output goes into the directory created when you run
369the build environment setup script (i.e. 369the build environment setup script (i.e.
370:ref:`structure-core-script`). By default, this :term:`Build Directory` 370:ref:`structure-core-script`). By default, this :term:`Build Directory`
@@ -428,7 +428,7 @@ relatively normal and the second is not:
428 build/tmp/sysroots/x86_64-linux/usr/bin 428 build/tmp/sysroots/x86_64-linux/usr/bin
429 429
430Even if the paths look unusual, 430Even if the paths look unusual,
431they both are correct - the first for a target and the second for a 431they both are correct --- the first for a target and the second for a
432native recipe. These paths are a consequence of the ``DESTDIR`` 432native recipe. These paths are a consequence of the ``DESTDIR``
433mechanism and while they appear strange, they are correct and in 433mechanism and while they appear strange, they are correct and in
434practice very effective. 434practice very effective.