12b641d3df
When building libpayload, make the build directory and .config outside libpayload source directory so it'll not pollute the libpayload source and cause conflicts with other builds. Change-Id: Idcfbc7dbe4d52a3559229d8450c3efaafd33b93b Signed-off-by: Iru Cai <mytbk920423@gmail.com> Reviewed-on: https://review.coreboot.org/14389 Tested-by: build bot (Jenkins) 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 | ||
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