0ffef882d8
It takes a long time for no gain: We don't need to update the submodules, we don't need to fetch the revision, we don't need to find the compilers, when all we want to do is to manipulate the .config file or clean the build directory. Change-Id: Ie1bd446a0d49a81e3cccdb56fe2c43ffd83b6c98 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-on: https://review.coreboot.org/18182 Tested-by: build bot (Jenkins) Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Reviewed-by: Martin Roth <martinroth@google.com> |
||
|---|---|---|
| .. | ||
| COPYING | ||
| Kconfig | ||
| Makefile | ||
| README | ||
| bootlog_module.c | ||
| cbfs_module.c | ||
| coreboot_module.c | ||
| coreinfo.c | ||
| coreinfo.h | ||
| cpuid.S | ||
| cpuinfo_module.c | ||
| multiboot_module.c | ||
| nvram_module.c | ||
| pci_module.c | ||
| ramdump_module.c | ||
| timestamps_module.c | ||
README
This is a silly little program that demonstrates how cool libpayload is and also serves a purpose. It is fun and educational! Requirements ------------ You should use the coreboot reference cross compiler. If you insist on using your system compiler, some Linux distributions might require you to install a package called gcc-multilib if you are on a 64bit system. Build ----- You need libpayload to build coreinfo. So, first, you need follow the README of libpayload to build it but install libpayload into its own directory by doing this: $ make DESTDIR=/path/to/libpayload/install install Then you can build coreinfo now: $ cd coreinfo $ make menuconfig $ make