local.conf 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264
  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. # Machine Selection
  15. #
  16. # You need to select a specific machine to target the build with. There are a selection
  17. # of emulated machines available which can boot and run in the QEMU emulator:
  18. #
  19. #MACHINE ?= "qemuarm"
  20. #MACHINE ?= "qemuarm64"
  21. #MACHINE ?= "qemumips"
  22. #MACHINE ?= "qemumips64"
  23. #MACHINE ?= "qemuppc"
  24. #MACHINE ?= "qemux86"
  25. #MACHINE ?= "qemux86-64"
  26. #
  27. # This sets the default machine to be qemux86-64 if no other machine is selected:
  28. MACHINE ??= "qemux86-64"
  29. #
  30. # Where to place downloads
  31. #
  32. # During a first build the system will download many different source code tarballs
  33. # from various upstream projects. This can take a while, particularly if your network
  34. # connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
  35. # can preserve this directory to speed up this part of subsequent builds. This directory
  36. # is safe to share between multiple builds on the same machine too.
  37. #
  38. # The default is a downloads directory under TOPDIR which is the build directory.
  39. #
  40. DL_DIR ?= "${TOPDIR}/../downloads"
  41. #
  42. # Where to place shared-state files
  43. #
  44. # BitBake has the capability to accelerate builds based on previously built output.
  45. # This is done using "shared state" files which can be thought of as cache objects
  46. # and this option determines where those files are placed.
  47. #
  48. # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
  49. # from these files if no changes were made to the configuration. If changes were made
  50. # to the configuration, only shared state files where the state was still valid would
  51. # be used (done using checksums).
  52. #
  53. # The default is a sstate-cache directory under TOPDIR.
  54. #
  55. SSTATE_DIR ?= "${TOPDIR}/../sstate-cache"
  56. #
  57. # Where to place the build output
  58. #
  59. # This option specifies where the bulk of the building work should be done and
  60. # where BitBake should place its temporary files and output. Keep in mind that
  61. # this includes the extraction and compilation of many applications and the toolchain
  62. # which can use Gigabytes of hard disk space.
  63. #
  64. # The default is a tmp directory under TOPDIR.
  65. #
  66. #TMPDIR = "${TOPDIR}/tmp"
  67. #
  68. # Package Management configuration
  69. #
  70. # This variable lists which packaging formats to enable. Multiple package backends
  71. # can be enabled at once and the first item listed in the variable will be used
  72. # to generate the root filesystems.
  73. # Options are:
  74. # - 'package_deb' for debian style deb files
  75. # - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
  76. # - 'package_rpm' for rpm style packages
  77. # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
  78. # We default to ipk:
  79. PACKAGE_CLASSES ?= "package_deb"
  80. #
  81. # SDK target architecture
  82. #
  83. # This variable specifies the architecture to build SDK items for and means
  84. # you can build the SDK packages for architectures other than the machine you are
  85. # running the build on (i.e. building i686 packages on an x86_64 host).
  86. # Supported values are i686 and x86_64
  87. #SDKMACHINE ?= "i686"
  88. #
  89. # Extra image configuration defaults
  90. #
  91. # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
  92. # images. Some of these options are added to certain image types automatically. The
  93. # variable can contain the following options:
  94. # "dbg-pkgs" - add -dbg packages for all installed packages
  95. # (adds symbol information for debugging/profiling)
  96. # "src-pkgs" - add -src packages for all installed packages
  97. # (adds source code for debugging)
  98. # "dev-pkgs" - add -dev packages for all installed packages
  99. # (useful if you want to develop against libs in the image)
  100. # "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
  101. # (useful if you want to run the package test suites)
  102. # "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
  103. # "tools-debug" - add debugging tools (gdb, strace)
  104. # "eclipse-debug" - add Eclipse remote debugging support
  105. # "tools-profile" - add profiling tools (oprofile, lttng, valgrind)
  106. # "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
  107. # "debug-tweaks" - make an image suitable for development
  108. # e.g. ssh root access has a blank password
  109. # There are other application targets that can be used here too, see
  110. # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
  111. # We default to enabling the debugging tweaks.
  112. EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
  113. EXTRA_IMAGE_FEATURES_remove = " dev-pkgs dbg-pkgs staticdev-pkgs tools-debug"
  114. IMAGE_FEATURES_remove = " dev-pkgs dbg-pkgs staticdev-pkgs tools-debug"
  115. #
  116. # Additional image features
  117. #
  118. # The following is a list of additional classes to use when building images which
  119. # enable extra features. Some available options which can be included in this variable
  120. # are:
  121. # - 'buildstats' collect build statistics
  122. # - 'image-mklibs' to reduce shared library files size for an image
  123. # - 'image-prelink' in order to prelink the filesystem image
  124. # NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
  125. # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
  126. USER_CLASSES ?= "buildstats image-mklibs image-prelink"
  127. #
  128. # Runtime testing of images
  129. #
  130. # The build system can test booting virtual machine images under qemu (an emulator)
  131. # after any root filesystems are created and run tests against those images. It can also
  132. # run tests against any SDK that are built. To enable this uncomment these lines.
  133. # See classes/test{image,sdk}.bbclass for further details.
  134. #IMAGE_CLASSES += "testimage testsdk"
  135. #TESTIMAGE_AUTO_qemuall = "1"
  136. #
  137. # Interactive shell configuration
  138. #
  139. # Under certain circumstances the system may need input from you and to do this it
  140. # can launch an interactive shell. It needs to do this since the build is
  141. # multithreaded and needs to be able to handle the case where more than one parallel
  142. # process may require the user's attention. The default is iterate over the available
  143. # terminal types to find one that works.
  144. #
  145. # Examples of the occasions this may happen are when resolving patches which cannot
  146. # be applied, to use the devshell or the kernel menuconfig
  147. #
  148. # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
  149. # Note: currently, Konsole support only works for KDE 3.x due to the way
  150. # newer Konsole versions behave
  151. #OE_TERMINAL = "auto"
  152. # By default disable interactive patch resolution (tasks will just fail instead):
  153. PATCHRESOLVE = "noop"
  154. #
  155. # Disk Space Monitoring during the build
  156. #
  157. # Monitor the disk space during the build. If there is less that 1GB of space or less
  158. # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
  159. # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
  160. # of the build. The reason for this is that running completely out of space can corrupt
  161. # files and damages the build in ways which may not be easily recoverable.
  162. # It's necessary to monitor /tmp, if there is no space left the build will fail
  163. # with very exotic errors.
  164. BB_DISKMON_DIRS ??= "\
  165. STOPTASKS,${TMPDIR},1G,100K \
  166. STOPTASKS,${DL_DIR},1G,100K \
  167. STOPTASKS,${SSTATE_DIR},1G,100K \
  168. STOPTASKS,/tmp,100M,100K \
  169. ABORT,${TMPDIR},100M,1K \
  170. ABORT,${DL_DIR},100M,1K \
  171. ABORT,${SSTATE_DIR},100M,1K \
  172. ABORT,/tmp,10M,1K"
  173. #
  174. # Shared-state files from other locations
  175. #
  176. # As mentioned above, shared state files are prebuilt cache data objects which can
  177. # used to accelerate build time. This variable can be used to configure the system
  178. # to search other mirror locations for these objects before it builds the data itself.
  179. #
  180. # This can be a filesystem directory, or a remote url such as http or ftp. These
  181. # would contain the sstate-cache results from previous builds (possibly from other
  182. # machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
  183. # cache locations to check for the shared objects.
  184. # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
  185. # at the end as shown in the examples below. This will be substituted with the
  186. # correct path within the directory structure.
  187. #SSTATE_MIRRORS ?= "\
  188. #file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
  189. #file://.* file:///some/local/dir/sstate/PATH"
  190. #
  191. # Qemu configuration
  192. #
  193. # By default qemu will build with a builtin VNC server where graphical output can be
  194. # seen. The two lines below enable the SDL backend too. By default libsdl2-native will
  195. # be built, if you want to use your host's libSDL instead of the minimal libsdl built
  196. # by libsdl2-native then uncomment the ASSUME_PROVIDED line below.
  197. PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
  198. PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
  199. #ASSUME_PROVIDED += "libsdl2-native"
  200. #
  201. # Hash Equivalence
  202. #
  203. # Enable support for automatically running a local hash equivalence server and
  204. # instruct bitbake to use a hash equivalence aware signature generator. Hash
  205. # equivalence improves reuse of sstate by detecting when a given sstate
  206. # artifact can be reused as equivalent, even if the current task hash doesn't
  207. # match the one that generated the artifact.
  208. #
  209. # A shared hash equivalent server can be set with "<HOSTNAME>:<PORT>" format
  210. #
  211. #BB_HASHSERVE = "auto"
  212. #BB_SIGNATURE_HANDLER = "OEEquivHash"
  213. #
  214. # Memory Resident Bitbake
  215. #
  216. # Bitbake's server component can stay in memory after the UI for the current command
  217. # has completed. This means subsequent commands can run faster since there is no need
  218. # for bitbake to reload cache files and so on. Number is in seconds, after which the
  219. # server will shut down.
  220. #
  221. #BB_SERVER_TIMEOUT = "60"
  222. # CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
  223. # track the version of this file when it was generated. This can safely be ignored if
  224. # this doesn't mean anything to you.
  225. CONF_VERSION = "1"
  226. # Add commercial license to the whitelist
  227. LICENSE_FLAGS_WHITELIST = "commercial non-commercial"
  228. IMAGE_INSTALL_append = " "
  229. CONNECTIVITY_CHECK_URIS = "https://github.com/"
  230. # ------------------------------------
  231. # define KERNEL_DEVICETREE ?=
  232. # dts_FM_100P_DPU_HDMI_DSI_V1.txt
  233. # dts_FM_100P_GPU_NPU_V1.txt
  234. # dts_FM_100P_NPU_GPU_FCE_V1.txt
  235. # dts_FM_100P_SOC_BASE_V1.txt
  236. # ------------------------------------
  237. # KERNEL_DEVICETREE = "dts_FM_100P_SOC_BASE_V1.dtb"
  238. SYSROOT_PREFIX = ""
  239. GLIBC_GIT_URI = "git://git@gitee.com/t-head-linux/glibc.git;protocol=https"
  240. BINUTILS_GIT_URI ?= "git://git@gitee.com/t-head-linux/binutils-gdb.git;branch=binutils-2_35-branch;protocol=https"