VirtualBox

source: kBuild/trunk/dist/debian/control@ 2754

Last change on this file since 2754 was 2251, checked in by bird, 16 years ago

debian/control: drop libacl1-dev dependency. References #66.

File size: 1.4 KB
Line 
1Source: kbuild
2Section: devel
3Priority: extra
4Maintainer: Torsten Werner <[email protected]>
5Build-Depends: autoconf, automake, byacc, cdbs, cvs, debhelper (>= 5), flex,
6 quilt
7Standards-Version: 3.8.0
8Homepage: http://svn.netlabs.org/kbuild
9Vcs-Svn: https://bollin.googlecode.com/svn/kbuild/trunk
10Vcs-Browser: http://bollin.googlecode.com/svn/kbuild/trunk
11
12Package: kbuild
13Architecture: any
14Depends: ${shlibs:Depends}, ${misc:Depends}
15Description: 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.
Note: See TracBrowser for help on using the repository browser.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette