diff options
Diffstat (limited to 'meta-yocto/conf/local.conf.sample')
-rw-r--r-- | meta-yocto/conf/local.conf.sample | 235 |
1 files changed, 235 insertions, 0 deletions
diff --git a/meta-yocto/conf/local.conf.sample b/meta-yocto/conf/local.conf.sample new file mode 100644 index 0000000000..31e760544f --- /dev/null +++ b/meta-yocto/conf/local.conf.sample | |||
@@ -0,0 +1,235 @@ | |||
1 | # | ||
2 | # This file is your local configuration file and is where all local user settings | ||
3 | # are placed. The comments in this file give some guide to the options a new user | ||
4 | # to the system might want to change but pretty much any configuration option can | ||
5 | # be set in this file. More adventurous users can look at local.conf.extended | ||
6 | # which contains other examples of configuration which can be placed in this file | ||
7 | # but new users likely won't need any of them initially. | ||
8 | # | ||
9 | # Lines starting with the '#' character are commented out and in some cases the | ||
10 | # default values are provided as comments to show people example syntax. Enabling | ||
11 | # the option is a question of removing the # character and making any change to the | ||
12 | # variable as required. | ||
13 | |||
14 | # | ||
15 | # Parallelism Options | ||
16 | # | ||
17 | # These two options control how much parallelism BitBake should use. The first | ||
18 | # option determines how many tasks bitbake should run in parallel: | ||
19 | # | ||
20 | #BB_NUMBER_THREADS ?= "4" | ||
21 | # | ||
22 | # The second option controls how many processes make should run in parallel when | ||
23 | # running compile tasks: | ||
24 | # | ||
25 | #PARALLEL_MAKE ?= "-j 4" | ||
26 | # | ||
27 | # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would | ||
28 | # be appropriate for example. | ||
29 | |||
30 | # | ||
31 | # Machine Selection | ||
32 | # | ||
33 | # You need to select a specific machine to target the build with. There are a selection | ||
34 | # of emulated machines available which can boot and run in the QEMU emulator: | ||
35 | # | ||
36 | #MACHINE ?= "qemuarm" | ||
37 | #MACHINE ?= "qemumips" | ||
38 | #MACHINE ?= "qemuppc" | ||
39 | #MACHINE ?= "qemux86" | ||
40 | #MACHINE ?= "qemux86-64" | ||
41 | # | ||
42 | # There are also the following hardware board target machines included for | ||
43 | # demonstration purposes: | ||
44 | # | ||
45 | #MACHINE ?= "beagleboard" | ||
46 | #MACHINE ?= "genericx86" | ||
47 | #MACHINE ?= "genericx86-64" | ||
48 | #MACHINE ?= "mpc8315e-rdb" | ||
49 | #MACHINE ?= "routerstationpro" | ||
50 | # | ||
51 | # This sets the default machine to be qemux86 if no other machine is selected: | ||
52 | MACHINE ??= "qemux86" | ||
53 | |||
54 | # | ||
55 | # Where to place downloads | ||
56 | # | ||
57 | # During a first build the system will download many different source code tarballs | ||
58 | # from various upstream projects. This can take a while, particularly if your network | ||
59 | # connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you | ||
60 | # can preserve this directory to speed up this part of subsequent builds. This directory | ||
61 | # is safe to share between multiple builds on the same machine too. | ||
62 | # | ||
63 | # The default is a downloads directory under TOPDIR which is the build directory. | ||
64 | # | ||
65 | #DL_DIR ?= "${TOPDIR}/downloads" | ||
66 | |||
67 | # | ||
68 | # Where to place shared-state files | ||
69 | # | ||
70 | # BitBake has the capability to accelerate builds based on previously built output. | ||
71 | # This is done using "shared state" files which can be thought of as cache objects | ||
72 | # and this option determines where those files are placed. | ||
73 | # | ||
74 | # You can wipe out TMPDIR leaving this directory intact and the build would regenerate | ||
75 | # from these files if no changes were made to the configuration. If changes were made | ||
76 | # to the configuration, only shared state files where the state was still valid would | ||
77 | # be used (done using checksums). | ||
78 | # | ||
79 | # The default is a sstate-cache directory under TOPDIR. | ||
80 | # | ||
81 | #SSTATE_DIR ?= "${TOPDIR}/sstate-cache" | ||
82 | |||
83 | # | ||
84 | # Where to place the build output | ||
85 | # | ||
86 | # This option specifies where the bulk of the building work should be done and | ||
87 | # where BitBake should place its temporary files and output. Keep in mind that | ||
88 | # this includes the extraction and compilation of many applications and the toolchain | ||
89 | # which can use Gigabytes of hard disk space. | ||
90 | # | ||
91 | # The default is a tmp directory under TOPDIR. | ||
92 | # | ||
93 | #TMPDIR = "${TOPDIR}/tmp" | ||
94 | |||
95 | # | ||
96 | # Default policy config | ||
97 | # | ||
98 | # The distribution setting controls which policy settings are used as defaults. | ||
99 | # The default value is fine for general Yocto project use, at least initially. | ||
100 | # Ultimately when creating custom policy, people will likely end up subclassing | ||
101 | # these defaults. | ||
102 | # | ||
103 | DISTRO ?= "poky" | ||
104 | # As an example of a subclass there is a "bleeding" edge policy configuration | ||
105 | # where many versions are set to the absolute latest code from the upstream | ||
106 | # source control systems. This is just mentioned here as an example, its not | ||
107 | # useful to most new users. | ||
108 | # DISTRO ?= "poky-bleeding" | ||
109 | |||
110 | # | ||
111 | # Package Management configuration | ||
112 | # | ||
113 | # This variable lists which packaging formats to enable. Multiple package backends | ||
114 | # can be enabled at once and the first item listed in the variable will be used | ||
115 | # to generate the root filesystems. | ||
116 | # Options are: | ||
117 | # - 'package_deb' for debian style deb files | ||
118 | # - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) | ||
119 | # - 'package_rpm' for rpm style packages | ||
120 | # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" | ||
121 | # We default to rpm: | ||
122 | PACKAGE_CLASSES ?= "package_rpm" | ||
123 | |||
124 | # | ||
125 | # SDK/ADT target architecture | ||
126 | # | ||
127 | # This variable specified the architecture to build SDK/ADT items for and means | ||
128 | # you can build the SDK packages for architectures other than the machine you are | ||
129 | # running the build on (i.e. building i686 packages on an x86_64 host._ | ||
130 | # Supported values are i686 and x86_64 | ||
131 | #SDKMACHINE ?= "i686" | ||
132 | |||
133 | # | ||
134 | # Extra image configuration defaults | ||
135 | # | ||
136 | # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated | ||
137 | # images. Some of these options are added to certain image types automatically. The | ||
138 | # variable can contain the following options: | ||
139 | # "dbg-pkgs" - add -dbg packages for all installed packages | ||
140 | # (adds symbol information for debugging/profiling) | ||
141 | # "dev-pkgs" - add -dev packages for all installed packages | ||
142 | # (useful if you want to develop against libs in the image) | ||
143 | # "ptest-pkgs" - add -ptest packages for all ptest-enabled packages | ||
144 | # (useful if you want to run the package test suites) | ||
145 | # "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) | ||
146 | # "tools-debug" - add debugging tools (gdb, strace) | ||
147 | # "eclipse-debug" - add Eclipse remote debugging support | ||
148 | # "tools-profile" - add profiling tools (oprofile, exmap, lttng, valgrind) | ||
149 | # "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) | ||
150 | # "debug-tweaks" - make an image suitable for development | ||
151 | # e.g. ssh root access has a blank password | ||
152 | # There are other application targets that can be used here too, see | ||
153 | # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. | ||
154 | # We default to enabling the debugging tweaks. | ||
155 | EXTRA_IMAGE_FEATURES = "debug-tweaks" | ||
156 | |||
157 | # | ||
158 | # Additional image features | ||
159 | # | ||
160 | # The following is a list of additional classes to use when building images which | ||
161 | # enable extra features. Some available options which can be included in this variable | ||
162 | # are: | ||
163 | # - 'buildstats' collect build statistics | ||
164 | # - 'image-mklibs' to reduce shared library files size for an image | ||
165 | # - 'image-prelink' in order to prelink the filesystem image | ||
166 | # - 'image-swab' to perform host system intrusion detection | ||
167 | # NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink | ||
168 | # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended | ||
169 | USER_CLASSES ?= "buildstats image-mklibs image-prelink" | ||
170 | |||
171 | # | ||
172 | # Runtime testing of images | ||
173 | # | ||
174 | # The build system can test booting virtual machine images under qemu (an emulator) | ||
175 | # after any root filesystems are created and run tests against those images. To | ||
176 | # enable this uncomment this line. See classes/testimage(-auto).bbclass for | ||
177 | # further details. | ||
178 | #TEST_IMAGE = "1" | ||
179 | # | ||
180 | # Interactive shell configuration | ||
181 | # | ||
182 | # Under certain circumstances the system may need input from you and to do this it | ||
183 | # can launch an interactive shell. It needs to do this since the build is | ||
184 | # multithreaded and needs to be able to handle the case where more than one parallel | ||
185 | # process may require the user's attention. The default is iterate over the available | ||
186 | # terminal types to find one that works. | ||
187 | # | ||
188 | # Examples of the occasions this may happen are when resolving patches which cannot | ||
189 | # be applied, to use the devshell or the kernel menuconfig | ||
190 | # | ||
191 | # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none | ||
192 | # Note: currently, Konsole support only works for KDE 3.x due to the way | ||
193 | # newer Konsole versions behave | ||
194 | #OE_TERMINAL = "auto" | ||
195 | # By default disable interactive patch resolution (tasks will just fail instead): | ||
196 | PATCHRESOLVE = "noop" | ||
197 | |||
198 | # | ||
199 | # Disk Space Monitoring during the build | ||
200 | # | ||
201 | # Monitor the disk space during the build. If there is less that 1GB of space or less | ||
202 | # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully | ||
203 | # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort | ||
204 | # of the build. The reason for this is that running completely out of space can corrupt | ||
205 | # files and damages the build in ways which may not be easily recoverable. | ||
206 | BB_DISKMON_DIRS = "\ | ||
207 | STOPTASKS,${TMPDIR},1G,100K \ | ||
208 | STOPTASKS,${DL_DIR},1G,100K \ | ||
209 | STOPTASKS,${SSTATE_DIR},1G,100K \ | ||
210 | ABORT,${TMPDIR},100M,1K \ | ||
211 | ABORT,${DL_DIR},100M,1K \ | ||
212 | ABORT,${SSTATE_DIR},100M,1K" | ||
213 | |||
214 | # | ||
215 | # Shared-state files from other locations | ||
216 | # | ||
217 | # As mentioned above, shared state files are prebuilt cache data objects which can | ||
218 | # used to accelerate build time. This variable can be used to configure the system | ||
219 | # to search other mirror locations for these objects before it builds the data itself. | ||
220 | # | ||
221 | # This can be a filesystem directory, or a remote url such as http or ftp. These | ||
222 | # would contain the sstate-cache results from previous builds (possibly from other | ||
223 | # machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the | ||
224 | # cache locations to check for the shared objects. | ||
225 | # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH | ||
226 | # at the end as shown in the examples below. This will be substituted with the | ||
227 | # correct path within the directory structure. | ||
228 | #SSTATE_MIRRORS ?= "\ | ||
229 | #file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ | ||
230 | #file://.* file:///some/local/dir/sstate/PATH" | ||
231 | |||
232 | # CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to | ||
233 | # track the version of this file when it was generated. This can safely be ignored if | ||
234 | # this doesn't mean anything to you. | ||
235 | CONF_VERSION = "1" | ||