From e3a3cc1009f0d45e22164d3845f4dfb9abfb21f4 Mon Sep 17 00:00:00 2001 From: Martin Roth Date: Thu, 18 Jan 2024 19:32:02 -0700 Subject: Documentation: Update Makefile .inc references to .mk Signed-off-by: Martin Roth Change-Id: I464170e60a22f39225044c6794d091455d931e9c Reviewed-on: https://review.coreboot.org/c/coreboot/+/80128 Reviewed-by: Felix Singer Tested-by: build bot (Jenkins) Reviewed-by: Felix Held --- Documentation/getting_started/build_system.md | 10 +++++----- Documentation/getting_started/kconfig.md | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) (limited to 'Documentation/getting_started') diff --git a/Documentation/getting_started/build_system.md b/Documentation/getting_started/build_system.md index 4013bc6057..35ed187989 100644 --- a/Documentation/getting_started/build_system.md +++ b/Documentation/getting_started/build_system.md @@ -7,10 +7,10 @@ to the point of providing its own custom language. The overhead of learning this new syntax is (hopefully) offset by its lower complexity. -The build system is defined in the toplevel `Makefile` and `toolchain.inc` +The build system is defined in the toplevel `Makefile` and `toolchain.mk` and is supposed to be generic (and is in fact used with a number of other projects). Project specific configuration should reside in files called -`Makefile.inc`. +`Makefile.mk`. In general, the build system provides a number of "classes" that describe various parts of the build. These cover the various build targets in coreboot @@ -36,7 +36,7 @@ TODO: explain how to create new classes and how to evaluate them. ### subdirs `subdirs` contains subdirectories (relative to the current directory) that should also be handled by the build system. The build system expects these -directories to contain a file called `Makefile.inc`. +directories to contain a file called `Makefile.mk`. Subdirectories are not read at the point where the `subdirs` statement resides but later, after the current directory is handled (and potentially @@ -66,7 +66,7 @@ supported options are: You can use the `add_intermediate` helper to add new post-processing steps for the final `coreboot.rom` image. For example you can add new files to CBFS by -adding something like this to `site-local/Makefile.inc` +adding something like this to `site-local/Makefile.mk` ``` $(call add_intermediate, add_mrc_data) @@ -100,4 +100,4 @@ The default implementation just returns `COREBOOT` (the default region) for all files. vboot provides its own implementation of `regions-for-file` that can be used -as reference in `src/vboot/Makefile.inc`. +as reference in `src/vboot/Makefile.mk`. diff --git a/Documentation/getting_started/kconfig.md b/Documentation/getting_started/kconfig.md index d40a4cc1ec..ddd32762a9 100644 --- a/Documentation/getting_started/kconfig.md +++ b/Documentation/getting_started/kconfig.md @@ -963,7 +963,7 @@ variable. This is not set in coreboot, which uses the default CONFIG_ prefix for all of its symbols. The coreboot makefile forces the config.h file to be included into all coreboot -C files. This is done in Makefile.inc on the compiler command line using the +C files. This is done in Makefile.mk on the compiler command line using the “-include $(obj)/config.h” command line option. Example of various symbol types in the config.h file: -- cgit v1.2.3