summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/ref-variables.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/poky-ref-manual/ref-variables.xml')
-rw-r--r--documentation/poky-ref-manual/ref-variables.xml37
1 files changed, 36 insertions, 1 deletions
diff --git a/documentation/poky-ref-manual/ref-variables.xml b/documentation/poky-ref-manual/ref-variables.xml
index 711a8a97ca..60bf034d19 100644
--- a/documentation/poky-ref-manual/ref-variables.xml
+++ b/documentation/poky-ref-manual/ref-variables.xml
@@ -344,7 +344,42 @@
344 344
345 <glossentry id='var-DL_DIR'><glossterm>DL_DIR</glossterm> 345 <glossentry id='var-DL_DIR'><glossterm>DL_DIR</glossterm>
346 <glossdef> 346 <glossdef>
347 <para>The directory where all fetched sources will be stored.</para> 347 <para>
348 The central download directory used by the build process to store downloads.
349 You can set this directory by defining the <filename>DL_DIR</filename>
350 variable in the <filename>/conf/local.conf</filename> file.
351 This directory is self-maintaining and you should not have
352 to touch it.
353 By default, the directory is <filename>downloads</filename> in the
354 Yocto Project build directory.
355 <literallayout class='monospaced'>
356 #DL_DIR ?= "${TOPDIR}/downloads"
357 </literallayout>
358 To specify a different download directory, simply uncomment the line
359 and provide your directory.
360 </para>
361
362 <para>
363 During a first build, the system downloads many different source code
364 tarballs from various upstream projects.
365 Downloading can take a while, particularly if your network
366 connection is slow.
367 Tarballs are all stored in the directory defined by
368 <filename>DL_DIR</filename> and the build system looks there first
369 to find source tarballs.
370 <note>
371 When wiping and rebuilding, you can preserve this directory to speed
372 up this part of subsequent builds.
373 </note>
374 </para>
375
376 <para>
377 You can safely share this directory between multiple builds on the
378 same development machine.
379 For additional information on how the build process gets source files, see
380 <link linkend='how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server'>this entry</link> in
381 The FAQ appendix of this manual.
382 </para>
348 </glossdef> 383 </glossdef>
349 384
350 </glossentry> 385 </glossentry>