blob: 9e7870c23f540aab7a5dd7e265cc2ef55d39c242 [file] [log] [blame]
Andrew Geissler84ad7c52020-06-27 00:00:16 -05001#
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# BASE = "${COREBASE}/../.."
15
16#
17# Machine Selection
18#
19# You need to select a specific machine to target the build with. There are a selection
20# of emulated machines available which can boot and run in the QEMU emulator:
21#
22# This sets the default machine if no other machine is selected:
23MACHINE ??= "qemuzynq"
24
25#
26# Where to place downloads
27#
28# During a first build the system will download many different source code tarballs
29# from various upstream projects. This can take a while, particularly if your network
30# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
31# can preserve this directory to speed up this part of subsequent builds. This directory
32# is safe to share between multiple builds on the same machine too.
33#
34# The default is a downloads directory under TOPDIR which is the build directory.
35#
36# DL_DIR ?= "${BASE}/downloads"
37
38#
39# Where to place shared-state files
40#
41# BitBake has the capability to accelerate builds based on previously built output.
42# This is done using "shared state" files which can be thought of as cache objects
43# and this option determines where those files are placed.
44#
45# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
46# from these files if no changes were made to the configuration. If changes were made
47# to the configuration, only shared state files where the state was still valid would
48# be used (done using checksums).
49#
50# The default is a sstate-cache directory under TOPDIR.
51#
52# SSTATE_DIR ?= "${BASE}/sstate-cache"
53
54#
55# Where to place the build output
56#
57# This option specifies where the bulk of the building work should be done and
58# where BitBake should place its temporary files and output. Keep in mind that
59# this includes the extraction and compilation of many applications and the toolchain
60# which can use Gigabytes of hard disk space.
61#
62# The default is a tmp directory under TOPDIR.
63#
64#TMPDIR = "${TOPDIR}/tmp"
65#
66#TMPDIR_versal = "${TOPDIR}/tmp-versal"
67
68#
69# Default policy config
70#
71# The distribution setting controls which policy settings are used as defaults.
72# The default value is fine for general Yocto project use, at least initially.
73# Ultimately when creating custom policy, people will likely end up subclassing
74# these defaults.
75#
76DISTRO ?= "petalinux"
77
78#
79# Package Management configuration
80#
81# This variable lists which packaging formats to enable. Multiple package backends
82# can be enabled at once and the first item listed in the variable will be used
83# to generate the root filesystems.
84# Options are:
85# - 'package_deb' for debian style deb files
86# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
87# - 'package_rpm' for rpm style packages
88# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
89# We default to rpm:
90PACKAGE_CLASSES ?= "package_rpm"
91
92#
93# SDK/ADT target architecture
94#
95# This variable specifies the architecture to build SDK/ADT items for and means
96# you can build the SDK packages for architectures other than the machine you are
97# running the build on (i.e. building i686 packages on an x86_64 host).
98# Supported values are i686 and x86_64
99#SDKMACHINE ?= "i686"
100
101#
102# Extra image configuration defaults
103#
104# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
105# images. Some of these options are added to certain image types automatically. The
106# variable can contain the following options:
107# "dbg-pkgs" - add -dbg packages for all installed packages
108# (adds symbol information for debugging/profiling)
109# "dev-pkgs" - add -dev packages for all installed packages
110# (useful if you want to develop against libs in the image)
111# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
112# (useful if you want to run the package test suites)
113# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
114# "tools-debug" - add debugging tools (gdb, strace)
115# "eclipse-debug" - add Eclipse remote debugging support
116# "tools-profile" - add profiling tools (oprofile, exmap, lttng, valgrind)
117# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
118# "debug-tweaks" - make an image suitable for development
119# e.g. ssh root access has a blank password
120# There are other application targets that can be used here too, see
121# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
122# We default to enabling the debugging tweaks.
123EXTRA_IMAGE_FEATURES = "debug-tweaks"
124
125#
126# Additional image features
127#
128# The following is a list of additional classes to use when building images which
129# enable extra features. Some available options which can be included in this variable
130# are:
131# - 'buildstats' collect build statistics
132# - 'image-mklibs' to reduce shared library files size for an image
133# - 'image-prelink' in order to prelink the filesystem image
134# - 'image-swab' to perform host system intrusion detection
135# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
136# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
137USER_CLASSES ?= "buildstats image-mklibs"
138
139#
140# Runtime testing of images
141#
142# The build system can test booting virtual machine images under qemu (an emulator)
143# after any root filesystems are created and run tests against those images. To
144# enable this uncomment this line. See classes/testimage(-auto).bbclass for
145# further details.
146#TEST_IMAGE = "1"
147#
148# Interactive shell configuration
149#
150# Under certain circumstances the system may need input from you and to do this it
151# can launch an interactive shell. It needs to do this since the build is
152# multithreaded and needs to be able to handle the case where more than one parallel
153# process may require the user's attention. The default is iterate over the available
154# terminal types to find one that works.
155#
156# Examples of the occasions this may happen are when resolving patches which cannot
157# be applied, to use the devshell or the kernel menuconfig
158#
159# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
160# Note: currently, Konsole support only works for KDE 3.x due to the way
161# newer Konsole versions behave
162#OE_TERMINAL = "auto"
163# By default disable interactive patch resolution (tasks will just fail instead):
164PATCHRESOLVE = "noop"
165
166#
167# Disk Space Monitoring during the build
168#
169# Monitor the disk space during the build. If there is less that 1GB of space or less
170# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
171# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
172# of the build. The reason for this is that running completely out of space can corrupt
173# files and damages the build in ways which may not be easily recoverable.
174# It's necesary to monitor /tmp, if there is no space left the build will fail
175# with very exotic errors.
176BB_DISKMON_DIRS = "\
177 STOPTASKS,${TMPDIR},1G,100K \
178 STOPTASKS,${DL_DIR},1G,100K \
179 STOPTASKS,${SSTATE_DIR},1G,100K \
180 STOPTASKS,/tmp,100M,100K \
181 ABORT,${TMPDIR},100M,1K \
182 ABORT,${DL_DIR},100M,1K \
183 ABORT,${SSTATE_DIR},100M,1K \
184 ABORT,/tmp,10M,1K"
185
186#
187# Shared-state files from other locations
188#
189# As mentioned above, shared state files are prebuilt cache data objects which can
190# used to accelerate build time. This variable can be used to configure the system
191# to search other mirror locations for these objects before it builds the data itself.
192#
193# This can be a filesystem directory, or a remote url such as http or ftp. These
194# would contain the sstate-cache results from previous builds (possibly from other
195# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
196# cache locations to check for the shared objects.
197# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
198# at the end as shown in the examples below. This will be substituted with the
199# correct path within the directory structure.
200#SSTATE_MIRRORS ?= "\
201#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
202#file://.* file:///some/local/dir/sstate/PATH"
203
Andrew Geissler7eb438a2020-11-30 19:53:16 -0600204XILINX_VER_MAIN = "2020.2"
Andrew Geissler84ad7c52020-06-27 00:00:16 -0500205
206# Uncomment below lines to provide path for custom xsct trim
207# This is required for building Versal based devices, please fetch the
208# xsct-trim from Xilinx lounge area
209#
Andrew Geissler7eb438a2020-11-30 19:53:16 -0600210#EXTERNAL_XSCT_TARBALL = "/proj/yocto/xsct-trim/2020.2_xsct_daily_latest"
Andrew Geissler84ad7c52020-06-27 00:00:16 -0500211#VALIDATE_XSCT_CHECKSUM = '0'
212
213# XILINX_VIVADO_DESIGN_SUIT should point to the Vivado installation directly if you are using xilinx-mcs recipe in meta-xilinx-tools
214#XILINX_VIVADO_DESIGN_SUIT = "/proj/xbuilds/2018.3_daily_latest/installs/lin64/Vivado/2018.3"
215
216# INHERIT += "externalsrc"
217# PREFERRED_PROVIDER_virtual/kernel = "linux-xlnx-dev"
218# EXTERNALSRC_pn-linux-xlnx-dev = "${BASE}/sources/linux"
219# RM_WORK_EXCLUDE += "linux-xlnx-dev"
220
221# PREFERRED_PROVIDER_virtual/bootloader = "u-boot-xlnx-dev"
222# EXTERNALSRC_pn-u-boot-xlnx-dev = "${BASE}/sources/u-boot"
223# RM_WORK_EXCLUDE += "u-boot-xlnx-dev"
224
225#Add below lines to use runqemu for ZU+ machines
Andrew Geisslera9ff2b32020-10-16 10:11:54 -0500226PMU_FIRMWARE_DEPLOY_DIR ??= "${DEPLOY_DIR_IMAGE}"
227PMU_FIRMWARE_IMAGE_NAME ??= "pmu-firmware-${MACHINE}"
Andrew Geissler84ad7c52020-06-27 00:00:16 -0500228
229# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
230# track the version of this file when it was generated. This can safely be ignored if
231# this doesn't mean anything to you.
232CONF_VERSION = "1"
233
Andrew Geisslera9ff2b32020-10-16 10:11:54 -0500234#Enable the below line to use pmu-rom.elf from a specific path
235#PMU_ROM = "/proj/yocto/pmu-rom/pmu-rom.elf"