<feed xmlns='http://www.w3.org/2005/Atom'>
<title>efi-boot-shim.git/.gitmodules, branch 15.4</title>
<subtitle> (mirror of https://github.com/vyos/efi-boot-shim.git)
</subtitle>
<id>https://git.amelek.net/vyos/efi-boot-shim.git/atom?h=15.4</id>
<link rel='self' href='https://git.amelek.net/vyos/efi-boot-shim.git/atom?h=15.4'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/'/>
<updated>2021-03-09T21:52:53+00:00</updated>
<entry>
<title>build: Import gnu-efi as a submodule and build against it</title>
<updated>2021-03-09T21:52:53+00:00</updated>
<author>
<name>Matthew Garrett</name>
<email>mjg59@google.com</email>
</author>
<published>2021-02-19T21:47:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/efi-boot-shim.git/commit/?id=c61bfdc8a34fea1c6ea97ac0fb9c99f34f980381'/>
<id>urn:sha1:c61bfdc8a34fea1c6ea97ac0fb9c99f34f980381</id>
<content type='text'>
Shim is rather more friendly with EFI internals than most code, and as a
result can end up making assumptions that are out of step with those made
by gnu-efi. Since both projects are developed independently, and since
distributions are often trying to build versions of shim against whatever
version of gnu-efi they are shipping, this can result in awkward build
failures. The easiest way to handle this is to use a git submodule and
import a known-good version of shim directly into the build tree. Given
static linking, this will also make reproducible builds easier.

Plus some changes from pjones:
- Fix up some more include paths
- more fine grained clean rules
- use our make ARCH
- use an rhboot/ repo for the gnu-efi remote

Signed-off-by: Matthew Garrett &lt;mjg59@google.com&gt;
</content>
</entry>
</feed>
