local.conf.sample 8.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224
  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. # This sets the default machine to be qemuarm if no other machine is selected:
  20. MACHINE ??= "qemuarm"
  21. #
  22. # Isar Configuration Selection
  23. #
  24. # You need to select a specific distribution configuration which will used for both:
  25. # generation of buildchroot environment and target root filesystem.
  26. #
  27. # This sets the default distribution configuration:
  28. DISTRO ??= "debian-stretch"
  29. DISTRO_ARCH ??= "armhf"
  30. #
  31. # Multiple Configuration Selection
  32. #
  33. # If you want to use multiple configuration files for the build, list them in the
  34. # following option.
  35. #
  36. # This sets the default multiple configurations used:
  37. BBMULTICONFIG = " \
  38. qemuarm-stretch \
  39. qemuarm-buster \
  40. qemuarm-bullseye \
  41. qemuarm64-stretch \
  42. qemuarm64-buster \
  43. qemuarm64-bullseye \
  44. qemui386-stretch \
  45. qemui386-buster \
  46. qemui386-bullseye \
  47. qemuamd64-stretch \
  48. qemuamd64-buster \
  49. qemuamd64-buster-tgz \
  50. qemuamd64-bullseye \
  51. container-amd64-stretch \
  52. container-amd64-buster \
  53. container-amd64-bullseye \
  54. qemumipsel-stretch \
  55. qemumipsel-buster \
  56. qemumipsel-bullseye \
  57. qemuriscv64-sid-ports \
  58. bananapi-buster \
  59. de0-nano-soc-buster \
  60. hikey-stretch \
  61. nand-ubi-demo-buster \
  62. nanopi-neo-buster \
  63. stm32mp15x-buster \
  64. rpi-stretch \
  65. sifive-fu540-sid-ports \
  66. qemuarm64-focal \
  67. qemuamd64-focal \
  68. "
  69. #
  70. # Where to place downloads
  71. #
  72. # During a first build the system will download many different source code tarballs
  73. # from various upstream projects. This can take a while, particularly if your network
  74. # connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
  75. # can preserve this directory to speed up this part of subsequent builds. This directory
  76. # is safe to share between multiple builds on the same machine too.
  77. #
  78. # The default is a downloads directory under TOPDIR which is the build directory.
  79. #
  80. #DL_DIR ?= "${TOPDIR}/downloads"
  81. #
  82. # Where to place shared-state files
  83. #
  84. # BitBake has the capability to accelerate builds based on previously built output.
  85. # This is done using "shared state" files which can be thought of as cache objects
  86. # and this option determines where those files are placed.
  87. #
  88. # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
  89. # from these files if no changes were made to the configuration. If changes were made
  90. # to the configuration, only shared state files where the state was still valid would
  91. # be used (done using checksums).
  92. #
  93. # The default is a sstate-cache directory under TOPDIR.
  94. #
  95. #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
  96. #
  97. # Where to place the build output
  98. #
  99. # This option specifies where the bulk of the building work should be done and
  100. # where BitBake should place its temporary files and output. Keep in mind that
  101. # this includes the extraction and compilation of many applications and the toolchain
  102. # which can use Gigabytes of hard disk space.
  103. #
  104. # The default is a tmp directory under TOPDIR.
  105. #
  106. #TMPDIR = "${TOPDIR}/tmp"
  107. #
  108. # Interactive shell configuration
  109. #
  110. # Under certain circumstances the system may need input from you and to do this it
  111. # can launch an interactive shell. It needs to do this since the build is
  112. # multithreaded and needs to be able to handle the case where more than one parallel
  113. # process may require the user's attention. The default is iterate over the available
  114. # terminal types to find one that works.
  115. #
  116. # Examples of the occasions this may happen are when resolving patches which cannot
  117. # be applied, to use the devshell or the kernel menuconfig
  118. #
  119. # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
  120. # Note: currently, Konsole support only works for KDE 3.x due to the way
  121. # newer Konsole versions behave
  122. #OE_TERMINAL = "auto"
  123. # By default disable interactive patch resolution (tasks will just fail instead):
  124. PATCHRESOLVE = "noop"
  125. #
  126. # Disk Space Monitoring during the build
  127. #
  128. # Monitor the disk space during the build. If there is less that 1GB of space or less
  129. # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
  130. # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
  131. # of the build. The reason for this is that running completely out of space can corrupt
  132. # files and damages the build in ways which may not be easily recoverable.
  133. # It's necesary to monitor /tmp, if there is no space left the build will fail
  134. # with very exotic errors.
  135. BB_DISKMON_DIRS = "\
  136. STOPTASKS,${TMPDIR},1G,100K \
  137. STOPTASKS,${DL_DIR},1G,100K \
  138. STOPTASKS,${SSTATE_DIR},1G,100K \
  139. STOPTASKS,/tmp,100M,100K \
  140. ABORT,${TMPDIR},100M,1K \
  141. ABORT,${DL_DIR},100M,1K \
  142. ABORT,${SSTATE_DIR},100M,1K \
  143. ABORT,/tmp,10M,1K"
  144. # Isar MIRRORS in case of service unavailable
  145. MIRRORS ?= "git?://salsa\.debian\.org/debian/.* git://github.com/ilbers/BASENAME"
  146. #
  147. # Shared-state files from other locations
  148. #
  149. # As mentioned above, shared state files are prebuilt cache data objects which can
  150. # used to accelerate build time. This variable can be used to configure the system
  151. # to search other mirror locations for these objects before it builds the data itself.
  152. #
  153. # This can be a filesystem directory, or a remote url such as http or ftp. These
  154. # would contain the sstate-cache results from previous builds (possibly from other
  155. # machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
  156. # cache locations to check for the shared objects.
  157. # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
  158. # at the end as shown in the examples below. This will be substituted with the
  159. # correct path within the directory structure.
  160. #SSTATE_MIRRORS ?= "\
  161. #file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
  162. #file://.* file:///some/local/dir/sstate/PATH"
  163. # CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
  164. # track the version of this file when it was generated. This can safely be ignored if
  165. # this doesn't mean anything to you.
  166. CONF_VERSION = "1"
  167. #
  168. # The default list of extra packages to be installed.
  169. IMAGE_INSTALL = "hello-isar example-raw example-module-${KERNEL_NAME} enable-fsck isar-exclude-docs samefile hello isar-disable-apt-cache cowsay example-prebuilt"
  170. #
  171. # Enable cross-compilation support
  172. ISAR_CROSS_COMPILE ?= "0"
  173. #
  174. # Uncomment to enable 32-bit compat architecture support
  175. # NOTE: this works for amd64 and arm64 targets so far
  176. #ISAR_ENABLE_COMPAT_ARCH ?= "1"
  177. # Uncomment this to enable caching of all source packages.
  178. # Without this feature, only sources of packages downloaded with apt:// are downloaded.
  179. #BASE_REPO_FEATURES ?= "cache-deb-src"
  180. #
  181. # Uncomment this to enable use of cached base repository
  182. #ISAR_USE_CACHED_BASE_REPO ?= "1"
  183. #
  184. # You probably want to uncomment this as well to make sure the build
  185. # does not access the network
  186. #BB_NO_NETWORK ?= "1"
  187. # Set root password to 'root'
  188. # Password was encrypted using following command:
  189. # mkpasswd -m sha512crypt -R 10000
  190. # mkpasswd is part of the 'whois' package of Debian
  191. USERS += "root"
  192. USER_root[password] ??= "$6$rounds=10000$RXeWrnFmkY$DtuS/OmsAS2cCEDo0BF5qQsizIrq6jPgXnwv3PHqREJeKd1sXdHX/ayQtuQWVDHe0KIO0/sVH8dvQm1KthF0d/"
  193. GROUPS += "isar"
  194. GROUP_isar[flags] = "system"
  195. USERS += "isar"
  196. USER_isar[gid] = "isar"
  197. USER_isar[home] = "/var/lib/isar"
  198. USER_isar[comment] = "My isar user"
  199. USER_isar[flags] = "system create-home"
  200. USER_isar[password] = "isar"
  201. USER_isar[flags] += "clear-text-password"
  202. # Uncomment the below line to debug WIC.
  203. # WIC_CREATE_EXTRA_ARGS += "-D"