File: control

package info (click to toggle)
boost-build 2.0-m12-2
  • links: PTS
  • area: main
  • in suites: lenny, squeeze
  • size: 8,692 kB
  • ctags: 6,963
  • sloc: ansic: 39,914; sh: 9,086; python: 6,120; xml: 5,524; cpp: 1,467; yacc: 456; asm: 353; makefile: 184
file content (36 lines) | stat: -rw-r--r-- 1,758 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
Source: boost-build
Homepage: http://www.boost.org/doc/tools/build/index.html
Section: devel
Priority: optional
Maintainer: Debian Boost Team <pkg-boost-devel@lists.alioth.debian.org>
Uploaders: Steve M. Robbins <smr@debian.org>, Domenico Andreoli <cavok@debian.org>, Christophe Prud'homme <prudhomm@mit.edu>
Build-Depends: debhelper (>= 7)
Standards-Version: 3.8.0

Package: boost-build
Architecture: all
Depends: bjam (>> 3.1.9-1)
Description: cross-platform build system for C++ projects
 Boost.Build is an easy way to build C++ projects, everywhere. You
 name you executables and libraries and list their
 sources. Boost.Build takes care about compiling your sources with
 right options, creating static and shared libraries, making
 executables, and other chores -- whether you're using gcc, msvc, or a
 dozen more supported C++ compilers -- on Windows, OSX, Linux and
 commercial UNIX systems.
 .
 Some of the most important features:
 .
    * Simple and high level build description. 
    * Portability. Most important build properties have symbolic names that
      work everywhere. 
    * Variant builds. When you build the same project twice with different 
      properties, all produced files are placed in different directories, 
      so you can build with 2 versions of gcc, or both debug and 
      release variants in one invocation.
    * Global dependencies. No matter what directory you build in, Boost.Build 
      will always check all dependencies in your entire project, preventing
      inconsistent binaries. 
    * Usage requirements. A target can specify properties, like include paths
      and preprocessor defines, that are necessary to use it. Those properties
      will be automatically applied whenever the target is used.