summaryrefslogtreecommitdiff
path: root/test.c
diff options
context:
space:
mode:
authorPeter Jones <pjones@redhat.com>2021-07-23 14:31:46 -0400
committerPeter Jones <pjones@redhat.com>2021-09-07 17:05:04 -0400
commit97350bd6e02ceb0818e8bc0a2b2bc6adaf9c2092 (patch)
tree3938da2461cf083b8d40c6809b6622d836af7b15 /test.c
parente5a406b4655f75bb1a691acc73a18ac69cc87cb0 (diff)
downloadefi-boot-shim-97350bd6e02ceb0818e8bc0a2b2bc6adaf9c2092.tar.gz
efi-boot-shim-97350bd6e02ceb0818e8bc0a2b2bc6adaf9c2092.zip
tests: link all tests against libefivar
When writing new tests, if we get to the point where we have to use libefivar for something, it's very common that I accidentally link it in twice. When that happens, I typically spend an unfortunate amount of time staring at FLTO's mangled names before I figure out what I've done wrong. This patch makes all the tests link against libefivar, thereby avoiding the issue. Signed-off-by: Peter Jones <pjones@redhat.com>
Diffstat (limited to 'test.c')
-rw-r--r--test.c17
1 files changed, 0 insertions, 17 deletions
diff --git a/test.c b/test.c
index d9902ebc..39725a72 100644
--- a/test.c
+++ b/test.c
@@ -122,23 +122,6 @@ LogError_(const char *file, int line, const char *func, const CHAR16 *fmt, ...)
return EFI_SUCCESS;
}
-#ifndef HAVE_GET_VARIABLE_ATTR
-EFI_STATUS
-get_variable_attr(const CHAR16 * const var, UINT8 **data, UINTN *len,
- EFI_GUID owner, UINT32 *attributes)
-{
- return EFI_UNSUPPORTED;
-}
-#endif
-
-#ifndef HAVE_GET_VARIABLE
-EFI_STATUS
-get_variable(const CHAR16 * const var, UINT8 **data, UINTN *len, EFI_GUID owner)
-{
- return get_variable_attr(var, data, len, owner, NULL);
-}
-#endif
-
#ifndef HAVE_SHIM_LOCK_GUID
EFI_GUID SHIM_LOCK_GUID = {0x605dab50, 0xe046, 0x4300, {0xab, 0xb6, 0x3d, 0xd8, 0x10, 0xdd, 0x8b, 0x23 } };
#endif