1 ################################################################################
2 # Kconfig package infrastructure
4 # This file implements an infrastructure that eases development of
5 # package .mk files for packages that use kconfig for configuration files.
6 # It is based on the generic-package infrastructure, and inherits all of its
9 # See the Buildroot documentation for details on the usage of this
12 ################################################################################
14 ################################################################################
15 # inner-kconfig-package -- generates the make targets needed to support a
18 # argument 1 is the lowercase package name
19 # argument 2 is the uppercase package name, including a HOST_ prefix
21 # argument 3 is the uppercase package name, without the HOST_ prefix
23 # argument 4 is the type (target or host)
24 ################################################################################
26 define inner-kconfig-package
28 # Call the generic package infrastructure to generate the necessary
30 # Note: this must be done _before_ attempting to use $$($(2)_DIR) in a
31 # dependency expression
32 $(call inner-generic-package
,$(1),$(2),$(3),$(4))
35 $(2)_KCONFIG_EDITORS ?
= menuconfig
37 $(2)_KCONFIG_FIXUP_CMDS ?
=
38 $(2)_KCONFIG_FRAGMENT_FILES ?
=
40 # The config file as well as the fragments could be in-tree, so before
41 # depending on them the package should be extracted (and patched) first.
43 # Since those files only have a order-only dependency, make would treat
44 # any missing one as a "force" target:
45 # https://www.gnu.org/software/make/manual/make.html#Force-Targets
46 # and would forcibly any rule that depend on those files, causing a
47 # rebuild of the kernel each time make is called.
49 # So, we provide a recipe that checks all of those files exist, to
50 # overcome that standard make behaviour.
52 $$($(2)_KCONFIG_FILE
) $$($(2)_KCONFIG_FRAGMENT_FILES
): |
$(1)-patch
53 for f in
$$($(2)_KCONFIG_FILE
) $$($(2)_KCONFIG_FRAGMENT_FILES
); do \
54 if
[ ! -f
"$$$${f}" ]; then \
55 printf
"Kconfig fragment '%s' for '%s' does not exist\n" "$$$${f}" "$(1)"; \
60 # The specified source configuration file and any additional configuration file
61 # fragments are merged together to .config, after the package has been patched.
62 # Since the file could be a defconfig file it needs to be expanded to a
63 # full .config first. We use 'make oldconfig' because this can be safely
64 # done even when the package does not support defconfigs.
65 $$($(2)_DIR
)/.config
: $$($(2)_KCONFIG_FILE
) $$($(2)_KCONFIG_FRAGMENT_FILES
)
66 support
/kconfig
/merge_config.sh
-m
-O
$$(@D
) \
67 $$($(2)_KCONFIG_FILE
) $$($(2)_KCONFIG_FRAGMENT_FILES
)
68 $$(Q
)yes
"" |
$$($(2)_MAKE_ENV
) $$(MAKE
) -C
$$($(2)_DIR
) \
69 $$($(2)_KCONFIG_OPTS
) oldconfig
71 # In order to get a usable, consistent configuration, some fixup may be needed.
72 # The exact rules are specified by the package .mk file.
73 define $(2)_FIXUP_DOT_CONFIG
74 $$($(2)_KCONFIG_FIXUP_CMDS
)
75 $$(Q
)yes
"" |
$$($(2)_MAKE_ENV
) $$(MAKE
) -C
$$($(2)_DIR
) \
76 $$($(2)_KCONFIG_OPTS
) oldconfig
77 $$(Q
)touch
$$($(2)_DIR
)/.stamp_kconfig_fixup_done
80 $$($(2)_DIR
)/.stamp_kconfig_fixup_done
: $$($(2)_DIR
)/.config
81 $$(call
$(2)_FIXUP_DOT_CONFIG
)
83 # Before running configure, the configuration file should be present and fixed
84 $$($(2)_TARGET_CONFIGURE
): $$($(2)_DIR
)/.stamp_kconfig_fixup_done
86 # Only enable the foo-*config targets when the package is actually enabled.
87 # Note: the variable $(2)_KCONFIG_VAR is not related to the kconfig
88 # infrastructure, but defined by pkg-generic.mk. The generic infrastructure is
89 # already called above, so we can effectively use this variable.
90 ifeq ($$($$($(2)_KCONFIG_VAR
)),y
)
92 # FOO_KCONFIG_FILE is required
93 ifeq ($$(BR_BUILDING
),y
)
94 ifeq ($$($(2)_KCONFIG_FILE
),)
95 $$(error Internal error
: no value specified for
$(2)_KCONFIG_FILE
)
99 # Configuration editors (menuconfig, ...)
101 # We need to apply the configuration fixups right after a configuration
102 # editor exits, so that it is possible to save the configuration right
103 # after exiting an editor, and so the user always sees a .config file
104 # that is clean wrt. our requirements.
106 # Because commands in $(1)_FIXUP_KCONFIG are probably using $(@D), we
107 # need to have a valid @D set. But, because the configurators rules are
108 # not real files and do not contain the path to the package build dir,
109 # @D would be just '.' in this case. So, we use an intermediate rule
110 # with a stamp-like file which path is in the package build dir, so we
111 # end up having a valid @D.
113 $$(addprefix $(1)-,$$($(2)_KCONFIG_EDITORS
)): $(1)-%: $$($(2)_DIR
)/.kconfig_editor_
%
114 $$($(2)_DIR
)/.kconfig_editor_
%: $$($(2)_DIR
)/.stamp_kconfig_fixup_done
115 $$($(2)_MAKE_ENV
) $$(MAKE
) -C
$$($(2)_DIR
) \
116 $$($(2)_KCONFIG_OPTS
) $$(*)
117 rm -f
$$($(2)_DIR
)/.stamp_
{kconfig_fixup_done
,configured
,built
}
118 rm -f
$$($(2)_DIR
)/.stamp_
{target
,staging
,images
}_installed
119 $$(call
$(2)_FIXUP_DOT_CONFIG
)
121 # Saving back the configuration
123 # Ideally, that should directly depend on $$($(2)_DIR)/.stamp_kconfig_fixup_done,
124 # but that breaks the use-case in PR-8156 (from a clean tree):
125 # make menuconfig <- enable kernel, use an in-tree defconfig, save and exit
126 # make linux-menuconfig <- enable/disable whatever option, save and exit
127 # make menuconfig <- change to use a custom defconfig file, set a path, save and exit
128 # make linux-update-config <- should save to the new custom defconfig file
130 # Because of that use-case, saving the configuration can *not* directly
131 # depend on the stamp file, because it itself depends on the .config,
132 # which in turn depends on the (newly-set an non-existent) custom
135 # Instead, we use an PHONY rule that will catch that situation.
137 $(1)-check-configuration-done
:
138 @if
[ ! -f
$$($(2)_DIR
)/.stamp_kconfig_fixup_done
]; then \
139 echo
"$(1) is not yet configured"; \
143 $(1)-savedefconfig
: $(1)-check-configuration-done
144 $$($(2)_MAKE_ENV
) $$(MAKE
) -C
$$($(2)_DIR
) \
145 $$($(2)_KCONFIG_OPTS
) savedefconfig
147 # Target to copy back the configuration to the source configuration file
148 # Even though we could use 'cp --preserve-timestamps' here, the separate
149 # cp and 'touch --reference' is used for symmetry with $(1)-update-defconfig.
150 $(1)-update-config
: $(1)-check-configuration-done
151 @
$$(if
$$($(2)_KCONFIG_FRAGMENT_FILES
), \
152 echo
"Unable to perform $(1)-update-config when fragment files are set"; exit
1)
153 cp
-f
$$($(2)_DIR
)/.config
$$($(2)_KCONFIG_FILE
)
154 touch
--reference
$$($(2)_DIR
)/.config
$$($(2)_KCONFIG_FILE
)
156 # Note: make sure the timestamp of the stored configuration is not newer than
157 # the .config to avoid a useless rebuild. Note that, contrary to
158 # $(1)-update-config, the reference for 'touch' is _not_ the file from which
160 $(1)-update-defconfig
: $(1)-savedefconfig
161 @
$$(if
$$($(2)_KCONFIG_FRAGMENT_FILES
), \
162 echo
"Unable to perform $(1)-update-defconfig when fragment files are set"; exit
1)
163 cp
-f
$$($(2)_DIR
)/defconfig
$$($(2)_KCONFIG_FILE
)
164 touch
--reference
$$($(2)_DIR
)/.config
$$($(2)_KCONFIG_FILE
)
166 endif # package enabled
170 $(1)-update-defconfig \
172 $(1)-check-configuration-done \
173 $$($(2)_DIR
)/.kconfig_editor_
% \
174 $$(addprefix $(1)-,$$($(2)_KCONFIG_EDITORS
))
176 endef # inner-kconfig-package
178 ################################################################################
179 # kconfig-package -- the target generator macro for kconfig packages
180 ################################################################################
182 kconfig-package
= $(call inner-kconfig-package
,$(pkgname
),$(call UPPERCASE
,$(pkgname
)),$(call UPPERCASE
,$(pkgname
)),target
)