The goals of the kBuild framework:
- Similar behavior cross all supported platforms.
- Flexibility, don't create unnecessary restrictions preventing ad-hoc solutions.
- Makefile can very simple to write and maintain.
There are four concepts being tried out in the current kBuild incaration:
- One configuration file for a subtree automatically included.
- Target configuration templates as the primary mechanism for makefile simplification.
- Tools and SDKs for helping out the templates with flexibility.
- Non-recursive makefile method by using sub-makefiles.
kBuild does not provide any facilities for checking compiler/library/header configurations, that's not in its scope. If this is important for your project, check out the autoconf tool in the GNU build system. It is possible to use kBuild together with autoconf if you like, but you might just as well use the full GNU package.
On Debian systems, the kBuild binaries can be found in /usr/bin and its data files in /usr/share/kBuild.
This manual page was written by Daniel Baumann <firstname.lastname@example.org>, for the Debian project (but may be used by others).