Lines Matching full:directory

62    :term:`Build Directory`
65 script that is found in the Source Directory
67 :term:`TOPDIR` variable points to the Build Directory.
69 You have a lot of flexibility when creating the Build Directory.
70 Following are some examples that show how to create the directory. The
71 examples assume your :term:`Source Directory` is named ``poky``:
73 - Create the Build Directory inside your Source Directory and let
74 the name of the Build Directory default to ``build``:
81 - Create the Build Directory inside your home directory and
88 - Provide a directory path and specifically name the Build
89 Directory. Any intermediate folders in the pathname must exist.
90 This next example creates a Build Directory named
91 ``YP-&DISTRO;`` within the existing directory ``mybuilds``:
99 By default, the Build Directory contains :term:`TMPDIR`, which is a
100 temporary directory the build system uses for its work. :term:`TMPDIR` cannot
101 be under NFS. Thus, by default, the Build Directory cannot be under
102 NFS. However, if you need the Build Directory to be under NFS, you can
105 Build Directory.
126 :file:`conf/local.conf` configuration file in the :term:`Build Directory`
131 :term:`Source Directory`, define variables for specific hardware and are
143 layer, the top level ``meta-openembedded/`` directory is not itself an actual layer,
152 have a top-level directory that is itself an actual layer, as well as
157 a directory structure which contains multiple valid OpenEmbedded layers.
243 You can see the Metadata in the ``meta`` directory of the Yocto
343 :term:`Source Directory`
344 This term refers to the directory structure
354 Source Directory.
356 Sometimes you might hear the term "poky directory" used to refer to
357 this directory structure.
361 The OpenEmbedded build system does not support file or directory
362 names that contain spaces. Be sure that the Source Directory you
365 The Source Directory contains BitBake, Documentation, Metadata and
367 must have the Source Directory in place on your development system in
378 the Source Directory, if you do, the top-level directory name of the
379 Source Directory is derived from the Yocto Project release tarball.
382 results in a Source Directory whose root folder is named poky.
386 Directory created by unpacking a released tarball as compared to
390 files in the Source Directory are on top of the release and will
394 changes you make to the local Source Directory can be later applied