KCONFIG-CONF(1)

✨ NAME ✨

kconfig-conf β€” the standalone implementation of the Linux Kconfig parser, bestie πŸ’…

(it's the little toolkit that reads your Kconfig files and does the whole "what do you want your build to look like" thing, and it's giving main character energy fr fr)


🌸 SYNOPSIS 🌸

kconfig-conf [options] <KConfig_file>

so like, you give it options and a KConfig_file, and it does its thing. iconic.


πŸ’– DESCRIPTION πŸ’–

okay so, the kconfig toolkit? it fully speaks the Kconfig language. it implements the parser and the configuration support that goes with your KConfig files, and it respects the Linux kernel KConfig convention, no cap. 🫢

At configuration time, the squad is:

  • kconfig-mconf β€” based on ncurses (that's menuconfig)
  • kconfig-conf β€” based on dialog (that's config)
  • kconfig-gconf β€” based on GTK+ (that's gconfig)
  • kconfig-qconf β€” based on QT (that's qconfig)

And the associated tools, because the family is BIG:

  • kconfig-diff β€” displays symbols diff between .config files πŸ”

periodt. four frontends, one parser, zero notes. πŸ’–


πŸŽ€ OPTIONS πŸŽ€

  • --silentoldconfig β€” only for kconfig-conf, babes. it reloads a given .config and regenerates the header and command files accordingly. like a glow-up for your config files ✨
  • --allnoconfig β€” sets all boolean configuration to no. everything. no. respectfully declining all of it πŸ’€
  • --allyesconfig β€” sets all boolean configuration to yes. yes to everything, we're saying yes to life, we're saying yes to the function πŸ’…
  • --randconfig β€” generates a random configuration. chaos mode, spin the wheel, let fate decide 🎲

πŸ¦‹ ENVIRONMENT πŸ¦‹

🌈 Environment variables for '*config'

  • KCONFIG_CONFIG β€” you can use this env var to specify a default kernel config file name, and it overrides the default name of ".config". so you don't gotta keep typing the same name over and over, she's convenient like that.
  • KCONFIG_OVERWRITECONFIG β€” if you set KCONFIG_OVERWRITECONFIG in the environment, Kconfig will not break symlinks when .config is a symlink to somewhere else. like, it'll be nice to your symlinks. so thoughtful πŸ₯Ί
  • CONFIG_ β€” if you set CONFIG_ in the environment, Kconfig will prefix all symbols with its value when saving the configuration, instead of using the default, "CONFIG_". so you can rebrand your symbols, you go girl.

πŸ“ Environment variables for '{allyes/allmod/allno/rand}config'

  • KCONFIG_ALLCONFIG β€” the allyesconfig/allmodconfig/allnoconfig/randconfig variants can also use the environment variable KCONFIG_ALLCONFIG as a flag, or as a filename that contains config symbols that the user requires to be set to a specific value. πŸ‘‘

If KCONFIG_ALLCONFIG is used without a filename β€” where KCONFIG_ALLCONFIG == "" or KCONFIG_ALLCONFIG == "1" β€” then make *config checks for a file named "all{yes/mod/no/def/random}.config" (corresponding to the *config command that was used) for symbol values that are to be forced. if that file isn't found, it checks for a file named "all.config" to contain forced values. it's like a scavenger hunt but the prize is a working config 🧚

This enables you to create "miniature" config (miniconfig) or custom config files containing just the config symbols that you are interested in. then the kernel config system generates the full .config file, including symbols of your miniconfig file. it's giving curated. it's giving limited edition. ✨

This 'KCONFIG_ALLCONFIG' file is a config file which contains (usually a subset of all) preset config symbols. These variable settings are still subject to normal dependency checks. (so like, no skipping the rules bestie, the deps are watching πŸ™ˆ)

Examples:

KCONFIG_ALLCONFIG=custom-notebook.config make allnoconfig or
KCONFIG_ALLCONFIG=mini.config make allnoconfig or
make KCONFIG_ALLCONFIG=mini.config allnoconfig

These examples will disable most options (allnoconfig) but enable or disable the options that are explicitly listed in the specified mini-config files. so, mostly off, except the things you personally vouched for πŸ’…

⭐ Environment variables for 'randconfig'

  • KCONFIG_SEED β€” you can set this to the integer value used to seed the RNG, if you want to somehow debug the behaviour of the kconfig parser/frontends. If not set, the current time will be used. so the chaos is either reproducible or literally just whatever time it is πŸ•
  • KCONFIG_PROBABILITY β€” this variable can be used to skew the probabilities. See /usr/share/doc/kconfig-frontends/kconfig.txt.gz. (yes it's a whole lore document, go read it)

πŸ‘‘ Environment variables for 'silentoldconfig'

  • KCONFIG_NOSILENTUPDATE β€” if this variable has a non-blank value, it prevents silent kernel config updates (requires explicit updates). it said "no sneaky edits, ask me first" πŸ’€
  • KCONFIG_AUTOCONFIG β€” this environment variable can be set to specify the path name of the "auto.conf" file. Its default value is "include/config/auto.conf".
  • KCONFIG_TRISTATE β€” this environment variable can be set to specify the path name of the "tristate.conf" file. Its default value is "include/config/tristate.conf".
  • KCONFIG_AUTOHEADER β€” this environment variable can be set to specify the path name of the "autoconf.h" (header) file. Its default value is "include/generated/autoconf.h".

πŸŽ€ HISTORY πŸŽ€

June 2017 β€” this man page was originally compiled by Philippe Thierry (phil at reseau-libre dot com). a legend, honestly. 🫢


okay that's the whole thing bestie, go forth and configure responsibly πŸ’–βœ¨

sign-off szn: this was the kconfig-conf man page, written by Philippe Thierry, dated October 2017 β€” mwah, no notes, she ate πŸ‘‘πŸ’