775214b710
In order to enable changing the generated C configuration files manually, this patch introduces the target `diffconfig` to the build system. After generating the configuration files, a developer can manually modify these sources (which are placed under build/configs) and invoke `make diffconfig` to generate a patch that shows the made differences. Such patches can be registered to a build by invoking the `applydiffconfig` target. The build system will always apply them whenever the configuration files are regenerated. A typical workflow to create a patch is as follows. # The pre_build target relies on generated configuration files hypervisor$ make BOARD=xxx SCENARIO=yyy pre_build (manually edit files under build/configs/boards and build/configs/scenarios) hypervisor$ make diffconfig # Patch generated to build/config.patch hypervisor$ cp build/config.patch /path/to/patch The following steps apply apply the patch to another build. hypervisor$ make BOARD=xxx SCENARIO=yyy defconfig hypervisor$ make applydiffconfig PATCH=/path/to/patch-file-or-directory hypervisor$ make After any patch is registered for a build, the configuration files will be automatically regenerated the next time `make` is invoked. To show a list of registered patches for generated configuration files, invoke `make applydiffconfig` without specifying `PATCH`. v2: * Add target `applydiffconfig` which accepts a PATCH variable to register an arbitrary patch file or a directory containing patch file(s) for a build. `.config_patches` is no longer used. Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com> |
||
---|---|---|
.. | ||
makefile | ||
genconf.sh | ||
genld.sh |