blob: 0fcde42af990ee0aff2587eb22fbc29d0b60c33d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
# SPDX-License-Identifier: GPL-3.0-or-later
# can be overridden per-tree e.g. use mrchromebox
url="https://github.com/coreboot/coreboot.git"
bkup_url="https://review.coreboot.org/coreboot"
makeargs="UPDATED_SUBMODULES=1 CPUS=$XBMK_THREADS"
rev="8ce4c91c41da3f042979f92095149a85bc93227d"
# edk2 in lbmk is actually coreboot, but with a fake board config
# that turns on edk2. coreboot is patched to never delete tianocore
# source code.
# however, it is also patched not to download tianocore. we download
# it, using libreboot's submodules feature! for redundancy, and patching
# this is a lazy way to do edk2 without integrating it into lbmk, which
# would bloat lbmk. coreboot already does all the magic, and matt maintains
# it. why reinvent matt's perfect wheel?
# it costs about half a minute extra, to build one coreboot target,
# and then the build is used in bulk across boards. this is the leah
# way to do tianocore in your coreboot distribution.
# yes.
xarch="i386-elf" # hack. for building the fake coreboot target
# not a performance hurdle on releases, since we will also use
# that coreboot target, and thus we will use crossgcc there
tree="default"
# we will build crossgcc in here,
# with ours symlinking to it
fetch_depend="coreboot/default"
# not stable yet for lbmk releases.
# tianocore payloads will be disabled
# in coreboot targets that use them,
# and coreboot targets that only use
# edk2 will have release=n as well
release="n"
|
