Config.in-structure
-------------------

This document gives a brief overview of the used Config.in files used by
Buildroot. The tree below shows their paths (relative to $(TOPDIR)) and how they
are hooked together.

Config.in
	-> target/Config.in
		-> target/linux/{brcm,rb}-2.{4,6}/Config.in
	-> target/linux/Config.in
	-> package/Config.in
		-> package/Config.in.collections
		-> package/*/Config.in
		-> package/mypackage/Config.in
		-> package/Config.in.runtime


File Content Description
------------------------

Config.in:
	This file is the starting point for `mconf'. It does not contain
	prompted options itself, but sources all lower-level Config.in files
	together. Also declaration of meta options (not prompted, for internal
	use only) is done here.

target/Config.in:
	In this file supported target devices are listed, by sourcing the
	various device definitions (see regular expression above) together into
	a single menu. The supported target filesystems are directly defined in
	here.

target/linux/Config.in:
	Contains all kernel module definitions. For clarity, they are defined
	here regardless of them being provided by the kernel souces
	(KMOD_template) or as standalone kernel module (PKG_template).

package/Config.in:
	This file hooks all package definitions together by sourcing the
	Config.in for the package collections first, then the Config.in file of
	each package in `packages/'. The "Extra Stuff" menu containing the
	runtime configuration is defined here, which might change in near
	future.

package/Config.in.collections:
	Package collections and their contents are defined here.

package/*/Config.in:
	Single configuration prompt for each package. Although external modules
	are build inside the `package/' directory, they should not be defined in
	per package configs. `target/linux/Config.in' should be used instead.

