package/pkg-kconfig.mk

   1 ################################################################################
   2 # Kconfig package infrastructure
   3 #
   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
   7 # features.
   8 #
   9 # See the Buildroot documentation for details on the usage of this
  10 # infrastructure.
  11 #
  12 ################################################################################
  13
  14 ################################################################################
  15 # inner-kconfig-package -- generates the make targets needed to support a
  16 # kconfig package
  17 #
  18 #  argument 1 is the lowercase package name
  19 #  argument 2 is the uppercase package name, including a HOST_ prefix
  20 #             for host packages
  21 #  argument 3 is the uppercase package name, without the HOST_ prefix
  22 #             for host packages
  23 #  argument 4 is the type (target or host)
  24 ################################################################################
  25
  26 define inner-kconfig-package
  27
  28 # Call the generic package infrastructure to generate the necessary
  29 # make targets.
  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))
  33
  34 # Default values
  35 $(2)_KCONFIG_EDITORS ?= menuconfig
  36 $(2)_KCONFIG_OPTS ?=
  37 $(2)_KCONFIG_FIXUP_CMDS ?=
  38 $(2)_KCONFIG_FRAGMENT_FILES ?=
  39
  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.
  42 #
  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.
  48 #
  49 # So, we provide a recipe that checks all of those files exist, to
  50 # overcome that standard make behaviour.
  51 #
  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)"; \
  56                         exit 1; \
  57                 fi; \
  58         done
  59
  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
  70
  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
  78 endef
  79
  80 $$($(2)_DIR)/.stamp_kconfig_fixup_done: $$($(2)_DIR)/.config
  81         $$(call $(2)_FIXUP_DOT_CONFIG)
  82
  83 # Before running configure, the configuration file should be present and fixed
  84 $$($(2)_TARGET_CONFIGURE): $$($(2)_DIR)/.stamp_kconfig_fixup_done
  85
  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)
  91
  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)
  96 endif
  97 endif
  98
  99 # For the configurators, we do want to use the system-provided host
 100 # tools, not the ones we build. This is particularly true for
 101 # pkg-config; if we use our pkg-config (from host-pkgconf), then it
 102 # would not look for the .pc from the host, but we do need them,
 103 # especially to find ncurses, GTK+, Qt (resp. for menuconfig and
 104 # nconfig, gconfig, xconfig).
 105 # So we simply remove our PATH and PKG_CONFIG_* variables.
 106 $(2)_CONFIGURATOR_MAKE_ENV = \
 107         $$(filter-out PATH=% PKG_CONFIG=% PKG_CONFIG_SYSROOT_DIR=% PKG_CONFIG_LIBDIR=%,$$($(2)_MAKE_ENV))
 108
 109 # Configuration editors (menuconfig, ...)
 110 #
 111 # We need to apply the configuration fixups right after a configuration
 112 # editor exits, so that it is possible to save the configuration right
 113 # after exiting an editor, and so the user always sees a .config file
 114 # that is clean wrt. our requirements.
 115 #
 116 # Because commands in $(1)_FIXUP_KCONFIG are probably using $(@D), we
 117 # need to have a valid @D set. But, because the configurators rules are
 118 # not real files and do not contain the path to the package build dir,
 119 # @D would be just '.' in this case. So, we use an intermediate rule
 120 # with a stamp-like file which path is in the package build dir, so we
 121 # end up having a valid @D.
 122 #
 123 $$(addprefix $(1)-,$$($(2)_KCONFIG_EDITORS)): $(1)-%: $$($(2)_DIR)/.kconfig_editor_%
 124 $$($(2)_DIR)/.kconfig_editor_%: $$($(2)_DIR)/.stamp_kconfig_fixup_done
 125         $$($(2)_CONFIGURATOR_MAKE_ENV) $$(MAKE) -C $$($(2)_DIR) \
 126                 $$($(2)_KCONFIG_OPTS) $$(*)
 127         rm -f $$($(2)_DIR)/.stamp_{kconfig_fixup_done,configured,built}
 128         rm -f $$($(2)_DIR)/.stamp_{target,staging,images}_installed
 129         $$(call $(2)_FIXUP_DOT_CONFIG)
 130
 131 # Saving back the configuration
 132 #
 133 # Ideally, that should directly depend on $$($(2)_DIR)/.stamp_kconfig_fixup_done,
 134 # but that breaks the use-case in PR-8156 (from a clean tree):
 135 #   make menuconfig           <- enable kernel, use an in-tree defconfig, save and exit
 136 #   make linux-menuconfig     <- enable/disable whatever option, save and exit
 137 #   make menuconfig           <- change to use a custom defconfig file, set a path, save and exit
 138 #   make linux-update-config  <- should save to the new custom defconfig file
 139 #
 140 # Because of that use-case, saving the configuration can *not* directly
 141 # depend on the stamp file, because it itself depends on the .config,
 142 # which in turn depends on the (newly-set an non-existent) custom
 143 # defconfig file.
 144 #
 145 # Instead, we use an PHONY rule that will catch that situation.
 146 #
 147 $(1)-check-configuration-done:
 148         @if [ ! -f $$($(2)_DIR)/.stamp_kconfig_fixup_done ]; then \
 149                 echo "$(1) is not yet configured"; \
 150                 exit 1; \
 151         fi
 152
 153 $(1)-savedefconfig: $(1)-check-configuration-done
 154         $$($(2)_MAKE_ENV) $$(MAKE) -C $$($(2)_DIR) \
 155                 $$($(2)_KCONFIG_OPTS) savedefconfig
 156
 157 # Target to copy back the configuration to the source configuration file
 158 # Even though we could use 'cp --preserve-timestamps' here, the separate
 159 # cp and 'touch --reference' is used for symmetry with $(1)-update-defconfig.
 160 $(1)-update-config: $(1)-check-configuration-done
 161         @$$(if $$($(2)_KCONFIG_FRAGMENT_FILES), \
 162                 echo "Unable to perform $(1)-update-config when fragment files are set"; exit 1)
 163         cp -f $$($(2)_DIR)/.config $$($(2)_KCONFIG_FILE)
 164         touch --reference $$($(2)_DIR)/.config $$($(2)_KCONFIG_FILE)
 165
 166 # Note: make sure the timestamp of the stored configuration is not newer than
 167 # the .config to avoid a useless rebuild. Note that, contrary to
 168 # $(1)-update-config, the reference for 'touch' is _not_ the file from which
 169 # we copy.
 170 $(1)-update-defconfig: $(1)-savedefconfig
 171         @$$(if $$($(2)_KCONFIG_FRAGMENT_FILES), \
 172                 echo "Unable to perform $(1)-update-defconfig when fragment files are set"; exit 1)
 173         cp -f $$($(2)_DIR)/defconfig $$($(2)_KCONFIG_FILE)
 174         touch --reference $$($(2)_DIR)/.config $$($(2)_KCONFIG_FILE)
 175
 176 endif # package enabled
 177
 178 .PHONY: \
 179         $(1)-update-config \
 180         $(1)-update-defconfig \
 181         $(1)-savedefconfig \
 182         $(1)-check-configuration-done \
 183         $$($(2)_DIR)/.kconfig_editor_% \
 184         $$(addprefix $(1)-,$$($(2)_KCONFIG_EDITORS))
 185
 186 endef # inner-kconfig-package
 187
 188 ################################################################################
 189 # kconfig-package -- the target generator macro for kconfig packages
 190 ################################################################################
 191
 192 kconfig-package = $(call inner-kconfig-package,$(pkgname),$(call UPPERCASE,$(pkgname)),$(call UPPERCASE,$(pkgname)),target)