Pastebin launched a little side project called VERYVIRAL.com, check it out ;-) Want more features on Pastebin? Sign Up, it's FREE!
Guest

Untitled

By: a guest on Aug 2nd, 2013  |  syntax: None  |  size: 10.96 KB  |  views: 26  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  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 ?= "atom-pc"
  46. #MACHINE ?= "beagleboard"
  47. #MACHINE ?= "mpc8315e-rdb"
  48. #MACHINE ?= "routerstationpro"
  49. #
  50. # This sets the default machine to be qemux86 if no other machine is selected:
  51. #MACHINE ??= "qemux86"
  52.  
  53. MACHINE ??= "at91sam9x5ek"
  54.  
  55. #
  56. # Where to place downloads
  57. #
  58. # During a first build the system will download many different source code tarballs
  59. # from various upstream projects. This can take a while, particularly if your network
  60. # connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
  61. # can preserve this directory to speed up this part of subsequent builds. This directory
  62. # is safe to share between multiple builds on the same machine too.
  63. #
  64. # The default is a downloads directory under TOPDIR which is the build directory.
  65. #
  66. #DL_DIR ?= "${TOPDIR}/downloads"
  67.  
  68. #
  69. # Where to place shared-state files
  70. #
  71. # BitBake has the capability to accelerate builds based on previously built output.
  72. # This is done using "shared state" files which can be thought of as cache objects
  73. # and this option determines where those files are placed.
  74. #
  75. # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
  76. # from these files if no changes were made to the configuration. If changes were made
  77. # to the configuration, only shared state files where the state was still valid would
  78. # be used (done using checksums).
  79. #
  80. # The default is a sstate-cache directory under TOPDIR.
  81. #
  82. #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
  83.  
  84. #
  85. # Where to place the build output
  86. #
  87. # This option specifies where the bulk of the building work should be done and
  88. # where BitBake should place its temporary files and output. Keep in mind that
  89. # this includes the extraction and compilation of many applications and the toolchain
  90. # which can use Gigabytes of hard disk space.
  91. #
  92. # The default is a tmp directory under TOPDIR.
  93. #
  94. #TMPDIR = "${TOPDIR}/tmp"
  95.  
  96. #
  97. # Default policy config
  98. #
  99. # The distribution setting controls which policy settings are used as defaults.
  100. # The default value is fine for general Yocto project use, at least initially.
  101. # Ultimately when creating custom policy, people will likely end up subclassing
  102. # these defaults.
  103. #
  104.  
  105. DISTRO ?= "poky"
  106.  
  107. DISTRO_FEATURES = "alsa bluetooth keyboard usbgadget usbhost wifi ipv6 ppp"
  108.  
  109. # As an example of a subclass there is a "bleeding" edge policy configuration
  110. # where many versions are set to the absolute latest code from the upstream
  111. # source control systems. This is just mentioned here as an example, its not
  112. # useful to most new users.
  113. # DISTRO ?= "poky-bleeding"
  114.  
  115. #
  116. # Package Management configuration
  117. #
  118. # This variable lists which packaging formats to enable. Multiple package backends
  119. # can be enabled at once and the first item listed in the variable will be used
  120. # to generate the root filesystems.
  121. # Options are:
  122. #  - 'package_deb' for debian style deb files
  123. #  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
  124. #  - 'package_rpm' for rpm style packages
  125. # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
  126. # We default to rpm:
  127. #PACKAGE_CLASSES ?= "package_rpm"
  128.  
  129. PACKAGE_CLASSES ?= "package_ipk"
  130.  
  131. #
  132. # SDK/ADT target architecture
  133. #
  134. # This variable specified the architecture to build SDK/ADT items for and means
  135. # you can build the SDK packages for architectures other than the machine you are
  136. # running the build on (i.e. building i686 packages on an x86_64 host._
  137. # Supported values are i686 and x86_64
  138. #SDKMACHINE ?= "i686"
  139.  
  140. #
  141. # Extra image configuration defaults
  142. #
  143. # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
  144. # images. Some of these options are added to certain image types automatically. The
  145. # variable can contain the following options:
  146. #  "dbg-pkgs"       - add -dbg packages for all installed packages
  147. #                     (adds symbol information for debugging/profiling)
  148. #  "dev-pkgs"       - add -dev packages for all installed packages
  149. #                     (useful if you want to develop against libs in the image)
  150. #  "ptest-pkgs"     - add -ptest packages for all ptest-enabled packages
  151. #                     (useful if you want to run the package test suites)
  152. #  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
  153. #  "tools-debug"    - add debugging tools (gdb, strace)
  154. #  "eclipse-debug"  - add Eclipse remote debugging support
  155. #  "tools-profile"  - add profiling tools (oprofile, exmap, lttng, valgrind)
  156. #  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
  157. #  "debug-tweaks"   - make an image suitable for development
  158. #                     e.g. ssh root access has a blank password
  159. # There are other application targets that can be used here too, see
  160. # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
  161. # We default to enabling the debugging tweaks.
  162. EXTRA_IMAGE_FEATURES = "debug-tweaks"
  163.  
  164. #
  165. # Additional image features
  166. #
  167. # The following is a list of additional classes to use when building images which
  168. # enable extra features. Some available options which can be included in this variable
  169. # are:
  170. #   - 'buildstats' collect build statistics
  171. #   - 'image-mklibs' to reduce shared library files size for an image
  172. #   - 'image-prelink' in order to prelink the filesystem image
  173. #   - 'image-swab' to perform host system intrusion detection
  174. # NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
  175. # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
  176. USER_CLASSES ?= "buildstats image-mklibs image-prelink"
  177.  
  178. #
  179. # Runtime testing of images
  180. #
  181. # The build system can test booting virtual machine images under qemu (an emulator)
  182. # after any root filesystems are created and run tests against those images. To
  183. # enable this uncomment this line
  184. #IMAGETEST = "qemu"
  185. #
  186. # This variable controls which tests are run against virtual images if enabled
  187. # above. The following would enable bat, boot the test case under the sanity suite
  188. # and perform toolchain tests
  189. #TEST_SCEN = "sanity bat sanity:boot toolchain"
  190. #
  191. # Because of the QEMU booting slowness issue (see bug #646 and #618), the
  192. # autobuilder may suffer a timeout issue when running sanity tests. We introduce
  193. # the variable TEST_SERIALIZE here to reduce the time taken by the sanity tests.
  194. # It is set to 1 by default, which will boot the image and run cases in the same
  195. # image without rebooting or killing the machine instance. If it is set to 0, the
  196. # image will be copied and tested for each case, which will take longer but be
  197. # more precise.
  198. #TEST_SERIALIZE = "1"
  199.  
  200. #
  201. # Interactive shell configuration
  202. #
  203. # Under certain circumstances the system may need input from you and to do this it
  204. # can launch an interactive shell. It needs to do this since the build is
  205. # multithreaded and needs to be able to handle the case where more than one parallel
  206. # process may require the user's attention. The default is iterate over the available
  207. # terminal types to find one that works.
  208. #
  209. # Examples of the occasions this may happen are when resolving patches which cannot
  210. # be applied, to use the devshell or the kernel menuconfig
  211. #
  212. # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
  213. # Note: currently, Konsole support only works for KDE 3.x due to the way
  214. # newer Konsole versions behave
  215. #OE_TERMINAL = "auto"
  216. # By default disable interactive patch resolution (tasks will just fail instead):
  217. PATCHRESOLVE = "noop"
  218.  
  219. #
  220. # Disk Space Monitoring during the build
  221. #
  222. # Monitor the disk space during the build. If there is less that 1GB of space or less
  223. # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
  224. # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
  225. # of the build. The reason for this is that running completely out of space can corrupt
  226. # files and damages the build in ways which may not be easily recoverable.
  227. BB_DISKMON_DIRS = "\
  228.     STOPTASKS,${TMPDIR},1G,100K \
  229.     STOPTASKS,${DL_DIR},1G,100K \
  230.     STOPTASKS,${SSTATE_DIR},1G,100K \
  231.     ABORT,${TMPDIR},100M,1K \
  232.     ABORT,${DL_DIR},100M,1K \
  233.     ABORT,${SSTATE_DIR},100M,1K"
  234.  
  235. #
  236. # Shared-state files from other locations
  237. #
  238. # As mentioned above, shared state files are prebuilt cache data objects which can
  239. # used to accelerate build time. This variable can be used to configure the system
  240. # to search other mirror locations for these objects before it builds the data itself.
  241. #
  242. # This can be a filesystem directory, or a remote url such as http or ftp. These
  243. # would contain the sstate-cache results from previous builds (possibly from other
  244. # machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
  245. # cache locations to check for the shared objects.
  246. # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
  247. # at the end as shown in the examples below. This will be substituted with the
  248. # correct path within the directory structure.
  249. #SSTATE_MIRRORS ?= "\
  250. #file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
  251. #file://.* file:///some/local/dir/sstate/PATH"
  252.  
  253. # CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
  254. # track the version of this file when it was generated. This can safely be ignored if
  255. # this doesn't mean anything to you.
  256. CONF_VERSION = "1"
  257.  
  258. LICENSE_FLAGS_WHITELIST += "commercial"
  259. SYSVINIT_ENABLED_GETTYS = ""