1 | Source: kbuild
|
---|
2 | Section: devel
|
---|
3 | Priority: extra
|
---|
4 | Maintainer: Torsten Werner <[email protected]>
|
---|
5 | Build-Depends: autoconf, automake, byacc, cdbs, cvs, debhelper (>= 5), flex,
|
---|
6 | quilt
|
---|
7 | Standards-Version: 3.8.0
|
---|
8 | Homepage: http://svn.netlabs.org/kbuild
|
---|
9 | Vcs-Svn: https://bollin.googlecode.com/svn/kbuild/trunk
|
---|
10 | Vcs-Browser: http://bollin.googlecode.com/svn/kbuild/trunk
|
---|
11 |
|
---|
12 | Package: kbuild
|
---|
13 | Architecture: any
|
---|
14 | Depends: ${shlibs:Depends}, ${misc:Depends}
|
---|
15 | Description: framework for writing simple makefiles for complex tasks
|
---|
16 | The goals of the kBuild framework:
|
---|
17 | - Similar behavior cross all supported platforms.
|
---|
18 | - Flexibility, don't create unnecessary restrictions preventing ad-hoc
|
---|
19 | solutions.
|
---|
20 | - Makefile can very simple to write and maintain.
|
---|
21 | .
|
---|
22 | There are four concepts being tried out in the current kBuild incaration:
|
---|
23 | - One configuration file for a subtree automatically included.
|
---|
24 | - Target configuration templates as the primary mechanism for makefile
|
---|
25 | simplification.
|
---|
26 | - Tools and SDKs for helping out the templates with flexibility.
|
---|
27 | - Non-recursive makefile method by using sub-makefiles.
|
---|
28 | .
|
---|
29 | kBuild does not provide any facilities for checking compiler/library/header
|
---|
30 | configurations, that's not in its scope. If this is important for your
|
---|
31 | project, check out the autoconf tool in the GNU build system. It is possible
|
---|
32 | to use kBuild together with autoconf if you like, but you might just as well
|
---|
33 | use the full GNU package.
|
---|