boost/build
2
0
Fork 0
mirror of https://github.com/boostorg/build.git synced 2026-02-15 00:52:16 +00:00
Code Issues Projects Releases Wiki Activity

Merge outstanding 1.33 changes to trunk:

Browse Source 
* QNX/qcc support.
* STLport5 support.
* STLport support docs cleanup.
* kFreeBSD support.
* MinGW/MSYS support.


[SVN r31345]
This commit is contained in:
Rene Rivera
2005-10-16 15:34:27 +00:00
parent a736430389
commit 39d07df796
26 changed files with 498 additions and 626 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
historic/jam/src/README
View File

@@ -87,6 +87,7 @@ INSTALLING
SunOS4.1 SUNOS
Ultrix 4.2 ULTRIX
BeOS BEOS *
GNU/kFreeBSD KFREEBSD
* requires editing Makefile

7
historic/jam/src/build.jam
View File

@@ -216,6 +216,13 @@ toolset msvc cl : /Fe : -D
[ opt --debug : /MLd /DEBUG /Z7 /Od /Ob0 ]
-I$(--python-include)
: kernel32.lib advapi32.lib $(--python-lib) ;
## QNX 6.x GCC 3.x/2.95.3
toolset qcc qcc : "-o " : -D
: -pedantic
[ opt --release : [ opt --symbols : -g : -s ] -O3 -finline-functions ]
[ opt --debug : -g -O0 -fno-inline ]
-I$(--python-include)
: -L$(--python-lib[1]) -l$(--python-lib[2]) ;
## Sun Workshop 6 C++
toolset sunpro cc : "-o " : -D
:

32
historic/jam/src/build.sh
View File

@@ -1,6 +1,6 @@
#!/bin/sh
#~ Copyright 2002-2004 Rene Rivera.
#~ Copyright 2002-2005 Rene Rivera.
#~ Distributed under the Boost Software License, Version 1.0.
#~ (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)
@@ -68,8 +68,15 @@ Guess_Toolset ()
elif test_uname IRIX ; then BOOST_JAM_TOOLSET=mipspro
elif test_uname IRIX64 ; then BOOST_JAM_TOOLSET=mipspro
elif test_uname OSF1 ; then BOOST_JAM_TOOLSET=tru64cxx
elif test_path qcc ; then BOOST_JAM_TOOLSET=qcc
elif test_path gcc ; then BOOST_JAM_TOOLSET=gcc
elif test_path icc ; then BOOST_JAM_TOOLSET=intel-linux
elif test -r /opt/intel/cc/9.0/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET=intel-linux
BOOST_JAM_TOOLSET_ROOT=/opt/intel/cc/9.0
elif test -r /opt/intel_cc_80/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET=intel-linux
BOOST_JAM_TOOLSET_ROOT=/opt/intel_cc_80
elif test -r /opt/intel/compiler70/ia32/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET=intel-linux
BOOST_JAM_TOOLSET_ROOT=/opt/intel/compiler70/ia32/
@@ -113,7 +120,7 @@ BOOST_JAM_OPT_MKJAMBASE="-o bootstrap/mkjambase0"
BOOST_JAM_OPT_YYACC="-o bootstrap/yyacc0"
case $BOOST_JAM_TOOLSET in
mingw)
if test -r ${BOOST_JAM_TOOLSET_ROOT}bin/gcc -r ; then
if test -r ${BOOST_JAM_TOOLSET_ROOT}bin/gcc ; then
export PATH=${BOOST_JAM_TOOLSET_ROOT}bin:$PATH
fi
BOOST_JAM_CC="gcc -DNT"
@@ -128,7 +135,11 @@ case $BOOST_JAM_TOOLSET in
;;
intel-linux)
if test -r /opt/intel/compiler70/ia32/bin/iccvars.sh ; then
if test -r /opt/intel/cc/9.0/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET_ROOT=/opt/intel/cc/9.0/
elif test -r /opt/intel_cc_80/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET_ROOT=/opt/intel_cc_80/
elif test -r /opt/intel/compiler70/ia32/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET_ROOT=/opt/intel/compiler70/ia32/
elif test -r /opt/intel/compiler60/ia32/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET_ROOT=/opt/intel/compiler60/ia32/
@@ -136,6 +147,17 @@ case $BOOST_JAM_TOOLSET in
BOOST_JAM_TOOLSET_ROOT=/opt/intel/compiler50/ia32/
fi
if test -r ${BOOST_JAM_TOOLSET_ROOT}bin/iccvars.sh ; then
# iccvars doesn't change LD_RUN_PATH. We adjust LD_RUN_PATH
# here in order not to have to rely on ld.so.conf knowing the
# icc library directory. We do this before running iccvars.sh
# in order to allow a user to add modifications to LD_RUN_PATH
# in iccvars.sh.
if test -z "${LD_RUN_PATH}"; then
LD_RUN_PATH="${BOOST_JAM_TOOLSET_ROOT}lib"
else
LD_RUN_PATH="${BOOST_JAM_TOOLSET_ROOT}lib:${LD_RUN_PATH}"
fi
export LD_RUN_PATH
. ${BOOST_JAM_TOOLSET_ROOT}bin/iccvars.sh
fi
BOOST_JAM_CC=icc
@@ -188,6 +210,10 @@ case $BOOST_JAM_TOOLSET in
BOOST_JAM_OPT_YYACC="$BOOST_JAM_OPT_YYACC $CFLAGS $LIBS"
;;
qcc)
BOOST_JAM_CC=qcc
;;
*)
error_exit "Unknown toolset: $BOOST_JAM_TOOLSET"
;;

2
historic/jam/src/execunix.c
View File

@@ -11,7 +11,7 @@
# include <time.h>
# include <unistd.h> /* needed for vfork(), _exit() prototypes */
#if defined(sun) || defined(__sun)
#if defined(sun) || defined(__sun) || defined(linux)
#include <wait.h>
#endif

2
historic/jam/src/fileunix.c
View File

@@ -19,7 +19,7 @@
# include "newstr.h"
# include <stdio.h>
#if defined(sun) || defined(__sun)
#if defined(sun) || defined(__sun) || defined(linux)
# include <unistd.h> /* needed for read and close prototype */
#endif

6
historic/jam/src/jam.h
View File

@@ -313,11 +313,11 @@
# define NO_VFORK
# endif
# ifdef __QNX__
# define unix
# ifdef __QNXNTO__
# define OSMINOR "OS=QNXNTO"
# define OS_QNXNTO
# else
# define unix
# define OSMINOR "OS=QNX"
# define OS_QNX
# define NO_VFORK
@@ -385,6 +385,10 @@
# define OS_OPENBSD
# define unix
# endif
# if defined (__FreeBSD_kernel__) && !defined(__FreeBSD__)
# define OSMINOR "OS=KFREEBSD"
# define OS_KFREEBSD
# endif
# ifndef OSMINOR
# define OSMINOR "OS=UNKNOWN"
# endif

1
jam_src/README
View File

@@ -87,6 +87,7 @@ INSTALLING
SunOS4.1 SUNOS
Ultrix 4.2 ULTRIX
BeOS BEOS *
GNU/kFreeBSD KFREEBSD
* requires editing Makefile

7
jam_src/build.jam
View File

@@ -216,6 +216,13 @@ toolset msvc cl : /Fe : -D
[ opt --debug : /MLd /DEBUG /Z7 /Od /Ob0 ]
-I$(--python-include)
: kernel32.lib advapi32.lib $(--python-lib) ;
## QNX 6.x GCC 3.x/2.95.3
toolset qcc qcc : "-o " : -D
: -pedantic
[ opt --release : [ opt --symbols : -g : -s ] -O3 -finline-functions ]
[ opt --debug : -g -O0 -fno-inline ]
-I$(--python-include)
: -L$(--python-lib[1]) -l$(--python-lib[2]) ;
## Sun Workshop 6 C++
toolset sunpro cc : "-o " : -D
:

32
jam_src/build.sh
View File

@@ -1,6 +1,6 @@
#!/bin/sh
#~ Copyright 2002-2004 Rene Rivera.
#~ Copyright 2002-2005 Rene Rivera.
#~ Distributed under the Boost Software License, Version 1.0.
#~ (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)
@@ -68,8 +68,15 @@ Guess_Toolset ()
elif test_uname IRIX ; then BOOST_JAM_TOOLSET=mipspro
elif test_uname IRIX64 ; then BOOST_JAM_TOOLSET=mipspro
elif test_uname OSF1 ; then BOOST_JAM_TOOLSET=tru64cxx
elif test_path qcc ; then BOOST_JAM_TOOLSET=qcc
elif test_path gcc ; then BOOST_JAM_TOOLSET=gcc
elif test_path icc ; then BOOST_JAM_TOOLSET=intel-linux
elif test -r /opt/intel/cc/9.0/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET=intel-linux
BOOST_JAM_TOOLSET_ROOT=/opt/intel/cc/9.0
elif test -r /opt/intel_cc_80/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET=intel-linux
BOOST_JAM_TOOLSET_ROOT=/opt/intel_cc_80
elif test -r /opt/intel/compiler70/ia32/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET=intel-linux
BOOST_JAM_TOOLSET_ROOT=/opt/intel/compiler70/ia32/
@@ -113,7 +120,7 @@ BOOST_JAM_OPT_MKJAMBASE="-o bootstrap/mkjambase0"
BOOST_JAM_OPT_YYACC="-o bootstrap/yyacc0"
case $BOOST_JAM_TOOLSET in
mingw)
if test -r ${BOOST_JAM_TOOLSET_ROOT}bin/gcc -r ; then
if test -r ${BOOST_JAM_TOOLSET_ROOT}bin/gcc ; then
export PATH=${BOOST_JAM_TOOLSET_ROOT}bin:$PATH
fi
BOOST_JAM_CC="gcc -DNT"
@@ -128,7 +135,11 @@ case $BOOST_JAM_TOOLSET in
;;
intel-linux)
if test -r /opt/intel/compiler70/ia32/bin/iccvars.sh ; then
if test -r /opt/intel/cc/9.0/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET_ROOT=/opt/intel/cc/9.0/
elif test -r /opt/intel_cc_80/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET_ROOT=/opt/intel_cc_80/
elif test -r /opt/intel/compiler70/ia32/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET_ROOT=/opt/intel/compiler70/ia32/
elif test -r /opt/intel/compiler60/ia32/bin/iccvars.sh ; then
BOOST_JAM_TOOLSET_ROOT=/opt/intel/compiler60/ia32/
@@ -136,6 +147,17 @@ case $BOOST_JAM_TOOLSET in
BOOST_JAM_TOOLSET_ROOT=/opt/intel/compiler50/ia32/
fi
if test -r ${BOOST_JAM_TOOLSET_ROOT}bin/iccvars.sh ; then
# iccvars doesn't change LD_RUN_PATH. We adjust LD_RUN_PATH
# here in order not to have to rely on ld.so.conf knowing the
# icc library directory. We do this before running iccvars.sh
# in order to allow a user to add modifications to LD_RUN_PATH
# in iccvars.sh.
if test -z "${LD_RUN_PATH}"; then
LD_RUN_PATH="${BOOST_JAM_TOOLSET_ROOT}lib"
else
LD_RUN_PATH="${BOOST_JAM_TOOLSET_ROOT}lib:${LD_RUN_PATH}"
fi
export LD_RUN_PATH
. ${BOOST_JAM_TOOLSET_ROOT}bin/iccvars.sh
fi
BOOST_JAM_CC=icc
@@ -188,6 +210,10 @@ case $BOOST_JAM_TOOLSET in
BOOST_JAM_OPT_YYACC="$BOOST_JAM_OPT_YYACC $CFLAGS $LIBS"
;;
qcc)
BOOST_JAM_CC=qcc
;;
*)
error_exit "Unknown toolset: $BOOST_JAM_TOOLSET"
;;

2
jam_src/execunix.c
View File

@@ -11,7 +11,7 @@
# include <time.h>
# include <unistd.h> /* needed for vfork(), _exit() prototypes */
#if defined(sun) || defined(__sun)
#if defined(sun) || defined(__sun) || defined(linux)
#include <wait.h>
#endif

2
jam_src/fileunix.c
View File

@@ -19,7 +19,7 @@
# include "newstr.h"
# include <stdio.h>
#if defined(sun) || defined(__sun)
#if defined(sun) || defined(__sun) || defined(linux)
# include <unistd.h> /* needed for read and close prototype */
#endif

6
jam_src/jam.h
View File

@@ -313,11 +313,11 @@
# define NO_VFORK
# endif
# ifdef __QNX__
# define unix
# ifdef __QNXNTO__
# define OSMINOR "OS=QNXNTO"
# define OS_QNXNTO
# else
# define unix
# define OSMINOR "OS=QNX"
# define OS_QNX
# define NO_VFORK
@@ -385,6 +385,10 @@
# define OS_OPENBSD
# define unix
# endif
# if defined (__FreeBSD_kernel__) && !defined(__FreeBSD__)
# define OSMINOR "OS=KFREEBSD"
# define OS_KFREEBSD
# endif
# ifndef OSMINOR
# define OSMINOR "OS=UNKNOWN"
# endif

3
v1/allyourbase.jam
View File

@@ -345,6 +345,9 @@ else if $(UNIX)
case IRIX :
RANLIB ?= "" ;
case KFREEBSD :
CLONE ?= cp -fpd ;
case LINUX :
CLONE ?= cp -fpd ;

13
v1/boost-base.jam
View File

@@ -2688,7 +2688,11 @@ rule common-variant-tag ( toolset variant : properties * )
{
local version-number = [ get-values <version> : $(properties) ] ;
version-number ?= $(BOOST_VERSION) ;
version-tag = [ MATCH "^([^.]+)[.]([^.]+)" : $(version-number[1]) ] ;
version-tag = [ MATCH "^([^.]+)[.]([^.]+)[.]([^.]+)" : $(version-number[1]) ] ;
if $(version-tag[3]) = 0
{
version-tag = $(version-tag[1-2]) ;
}
version-tag = $(version-tag:J="_") ;
}
@@ -2946,6 +2950,13 @@ rule toolset::requirements ( toolset variant : subvariant-path properties * )
if <runtime-link>dynamic in $(properties) { requirements += <threading>multi ; }
}
}
if <stlport-version>5.0 in $(properties)
{
# STLPort-5 doesn't have any single-threaded builds, so we're going
# to force all such targets to be built with multithread support.
# This is essentially a usage-requirement on the stlport library.
requirements += <threading>multi ;
}
return $(subvariant-path) [ impose-requirements $(properties) : $(requirements) ] ;
}

139
v1/dmc-stlport-tools.html
View File

@@ -2,8 +2,6 @@
<html>
<head>
<meta name="generator" content=
"HTML Tidy for Linux/x86 (vers 1st September 2003), see www.w3.org">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="../../../boost.css">
@@ -39,140 +37,15 @@
test with multiple installed versions of STLPort, so that objects build in
each configuration will be built into separate directories.</p>
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>
<p>The <code>dmc-stlport</code> toolset responds to the following
variables, which can be set in the environment or configured on the jam
command-line using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. It is
an extension of the <a href="dmc-tools.html">dmc toolset</a> and therefore
responds to all of the Digital Mars <a href=
"dmc-tools.html#configuration">configuration variables</a> in addition to
those listed below.</p>
<p>In the table below, <i>version</i> corresponds to an STLPort version
number, e.g. "<code>4.5.3</code>".</p>
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
<th>Semantics</th>
<th>Default</th>
<th>Notes</th>
</tr>
<tr>
<td><code>STLPORT_PATH</code></td>
<td>A directory containing at least one subdirectory of the form
<code>/STLPort-</code><i>version</i> where an STLPort installation can
be found.</td>
<td><i>empty</i></td>
<td>Allows easy configuration for an installation where several STLPort
versions are installed under a single directory.</td>
</tr>
<tr>
<td><code>STLPORT_</code><i>version</i><code>_PATH</code></td>
<td>The directory where the specific STLPort <i>version</i>
installation can be found, in case there is no central location
appropriate for <code>STLPORT_PATH</code>, above, or a particular
version's installation is not located in the usual place.</td>
<td><i>empty</i></td>
<td>Allows configuration of a specific STLPort installation.</td>
</tr>
<tr>
<td><code>STLPORT_VERSION</code></td>
<td>The version of STLPort in use by default.</td>
<td><code>4.6.2</code></td>
<td>Other values can be selected in parallel setting the <a href=
"build_system.htm#initiating">build property</a>
&lt;stlport-version&gt; to values from the list of
<code>$(STLPORT_VERSIONS)</code></td>
</tr>
<tr>
<td><code>STLPORT_VERSIONS</code></td>
<td>A space-separated list of alternate versions of STLport available
on this machine.</td>
<td><code>4.6&nbsp;4.5.3&nbsp;4.5</code></td>
</tr>
</table>
<h2><a name="features" id="features">Toolset-Specific Features</a></h2>
<p>The following <code>dmc-stlport</code>-specific <a href=
"build_system.htm#features">features</a> can be used in target build
requirements or in the <a href=
"build_system.htm#initiating"><code>BUILD</code></a> variable:</p>
<table border="1" summary="features">
<tr>
<th>Feature</th>
<th>Values</th>
<th>Default</th>
<th>Semantics</th>
</tr>
<tr>
<td><code>stlport-iostream</code></td>
<td><code>off on</code></td>
<td><code>off</code></td>
<td>Controls whether STLPort's own iostreams are in use. Though this
setting is <code>off</code> by default to save users from having to
build STLPort, we strongly recommend <code>on</code> instead.</td>
</tr>
<tr>
<td><code>stlport-version</code></td>
<td><code>$(STLPORT_VERSION)&nbsp;$(STLPORT_VERSIONS)</code> (see
above)</td>
<td><code>$(STLPORT_VERSION)</code></td>
<td>Selects a version of STLPort for each target</td>
</tr>
<tr>
<td><code>stlport-cstd-namespace</code></td>
<td><code>std global</code></td>
<td><code>std</code></td>
<td>Controls whether or not names from the "C" library headers such as
&lt;cstdlib&gt; are imported into <code>namespace std</code>.</td>
</tr>
</table>
<p>In addition to what this toolset provides, configuration and extended
functionality is available through the common <a href=
"stlport.html">stlport library support</a>.</p>
<hr>
<p>Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
31 July, 2004
<!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Revised $Date$</p>
<p>Copyright &copy; Dave Abrahams 2002, Aleksey Gurtovoy 2004.</p>
<p>Copyright &copy; Dave Abrahams 2002, Aleksey Gurtovoy 2004, Rene Rivera
2005.</p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or

63
v1/gcc-stlport-tools.html
View File

@@ -2,8 +2,6 @@
<html>
<head>
<meta name="generator" content=
"HTML Tidy for Linux/x86 (vers 1st September 2003), see www.w3.org">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="../../../boost.css">
@@ -35,65 +33,14 @@
"http://www.stlport.org">STLport</a> as a replacement to the GNU
libg++.</p>
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The gcc-stlport toolset responds to the following
variables which can be set in the environment or configured on the jam
command-line using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. This
toolset is an extension to the <a href="gcc-tools.html">gcc toolset</a> and
therefore responds to all of the GCC <a href=
"gcc-tools.html#configuration">configuration variables</a> in addition to
those listed below.
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
<th>Semantics</th>
<th>Default</th>
<th>Notes</th>
</tr>
<tr>
<td><code>STLPORT_ROOT</code></td>
<td>Path to installation of STLport.</td>
<td>(none)</td>
<td>It is customary to set this in your "Jamrules" file.</td>
</tr>
<tr>
<td><code>STLPORT_INCLUDE_DIRECTORY</code></td>
<td>The name of the directory within the STLport installation
containing the header files.</td>
<td><code>stlport</code></td>
<td>&nbsp;</td>
</tr>
<tr>
<td><code>STLPORT_LIB_DIRECTORY</code></td>
<td>The name of the directory withint the STLport installation
containing the built libraries.</td>
<td><code>lib</code></td>
<td>&nbsp;</td>
</tr>
</table>
<p>In addition to what this toolset provides, configuration and extended
functionality is available through the common <a href=
"stlport.html">stlport library support</a>.</p>
<hr>
<p>Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
09 May, 2002 <!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Revised $Date$</p>
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p>Copyright &copy; Dave Abrahams 2002, Rene Rivera 2005.</p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or

10
v1/gcc-tools.jam
View File

@@ -1,5 +1,5 @@
# Copyright (c) 2001 David Abrahams.
# Copyright (c) 2002-2003 Rene Rivera.
# Copyright (c) 2002-2005 Rene Rivera.
# Distributed under the Boost Software License, Version 1.0.
# (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)
@@ -144,6 +144,10 @@ else if $(UNIX)
{
# gcc on HP-UX does not support multi-threading, don't set anything here
}
case QNX* :
{
# gcc/QCC on QNX is always? in multi-thread mode, don't set anything here
}
case * :
{
flags gcc CFLAGS <threading>multi : -pthread ;
@@ -416,7 +420,7 @@ rule Link-action
LNOPT on $(<) = "" ;
}
# do we use sonames or not?
if $(DLLVERSION) && $(TARGET_TYPE) in $(SHARED_TYPES) && ( $(OS) = LINUX || $(OS) = OPENBSD ) && ! $(NO_GNU_LN)
if $(DLLVERSION) && $(TARGET_TYPE) in $(SHARED_TYPES) && ( $(OS) = LINUX || $(OS) = OPENBSD || $(OS) = KFREEBSD ) && ! $(NO_GNU_LN)
{
OUTTAG on $(<) = ".$(DLLVERSION)" ;
SOTAG on $(<) = ".$(DLLVERSION)" ;
@@ -462,7 +466,7 @@ rule Link-action
gcc-spawn $(<) ;
gcc-Link-action $(<) : $(>) ;
if $(DLLVERSION) && $(TARGET_TYPE) in $(SHARED_TYPES) && ( $(OS) = LINUX || $(OS) = OPENBSD ) && ! $(NO_GNU_LN)
if $(DLLVERSION) && $(TARGET_TYPE) in $(SHARED_TYPES) && ( $(OS) = LINUX || $(OS) = OPENBSD || $(OS) = KFREEBSD ) && ! $(NO_GNU_LN)
{
return "$(<[1]).$(DLLVERSION)" ;
}

64
v1/mingw-stlport-tools.html
View File

@@ -2,7 +2,6 @@
<html>
<head>
<meta name="generator" content="fingers ;)">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="../../../boost.css">
@@ -35,67 +34,14 @@
"http://www.stlport.org">STLport</a> as a replacement to the GNU
libg++.</p>
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The mingw-stlport toolset responds to the following
variables which can be set in the environment or configured on the jam
command-line using <span style=
"white-space:nowrap;"><code>-s<i>VARIABLE_NAME</i>=</code><i>value</i></span>.
This toolset is an extension to the <a href="mingw-tools.html">mingw
toolset</a> and therefore responds to all of the MinGW <a href=
"mingw-tools.html#configuration">configuration variables</a> in addition to
those listed below.
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
<th>Semantics</th>
<th>Default</th>
<th>Notes</th>
</tr>
<tr>
<td><code>STLPORT_ROOT</code></td>
<td>Path to installation of STLport.</td>
<td>(none)</td>
<td>It is customary to set this in your "Jamrules" file.</td>
</tr>
<tr>
<td><code>STLPORT_INCLUDE_DIRECTORY</code></td>
<td>The name of the directory within the STLport installation
containing the header files.</td>
<td><code>stlport</code></td>
<td>&nbsp;</td>
</tr>
<tr>
<td><code>STLPORT_LIB_DIRECTORY</code></td>
<td>The name of the directory within the STLport installation
containing the built libraries.</td>
<td><code>lib</code></td>
<td>&nbsp;</td>
</tr>
</table>
<p>In addition to what this toolset provides, configuration and extended
functionality is available through the common <a href=
"stlport.html">stlport library support</a>.</p>
<hr>
<p>Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
12 August, 2004
<!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Revised $Date$</p>
<p>Copyright &copy; Janusz Piwowarski 2004.</p>
<p>Copyright &copy; Janusz Piwowarski 2004, Rene Rivera 2005.</p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or

4
v1/mingw-tools.jam
View File

@@ -13,6 +13,9 @@ set-as-singleton MINGW_ROOT_DIRECTORY MINGW_BIN_DIRECTORY MINGW_INCLUDE_DIRECTOR
local GCC_INCLUDE_DIRECTORY = $(MINGW_INCLUDE_DIRECTORY) ;
local GCC_STDLIB_DIRECTORY = $(MINGW_STDLIB_DIRECTORY) ;
extends-toolset gcc ;
# So that RUNPATH, and PATH, is set to include where the mingw DLLs are located.
flags mingw STDLIBPATH : $(GCC_BIN_DIRECTORY) ;
}
flags mingw LINKFLAGS <user-interface>gui : -Wl,--subsystem,windows ;
@@ -24,4 +27,3 @@ GCC_NO_EXPORT_ALL ?= true ;
# Use the -mno-cygwin flag for compiling C, C++ and linking
CFLAGS += -mno-cygwin ;
LINKFLAGS += -mno-cygwin ;

134
v1/msvc-stlport-tools.html
View File

@@ -2,8 +2,6 @@
<html>
<head>
<meta name="generator" content=
"HTML Tidy for Linux/x86 (vers 1st September 2003), see www.w3.org">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="../../../boost.css">
@@ -41,136 +39,14 @@
that objects build in each configuration will be built into separate
directories.</p>
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The <code>msvc</code> toolset responds to the following
variables, which can be set in the environment or configured on the jam
command-line using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. It is
an extension of the <a href="msvc-tools.html">msvc toolset</a> and
therefore responds to all of the MSVC <a href=
"msvc-tools.html#configuration">configuration variables</a> in addition to
those listed below.
<p>In the table below, <i>version</i> corresponds to an STLPort version
number, e.g. "<code>4.5.3</code>".</p>
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
<th>Semantics</th>
<th>Default</th>
<th>Notes</th>
</tr>
<tr>
<td><code>STLPORT_PATH</code></td>
<td>A directory containing at least one subdirectory of the form
<code>/STLPort-</code><i>version</i> where an STLPort installation can
be found.</td>
<td><i>empty</i></td>
<td>Allows easy configuration for an installation where several STLPort
versions are installed under a single directory.</td>
</tr>
<tr>
<td><code>STLPORT_</code><i>version</i><code>_PATH</code></td>
<td>The directory where the specific STLPort <i>version</i>
installation can be found, in case there is no central location
appropriate for <code>STLPORT_PATH</code>, above, or a particular
version's installation is not located in the usual place.</td>
<td><i>empty</i></td>
<td>Allows configuration of a specific STLPort installation.</td>
</tr>
<tr>
<td><code>STLPORT_VERSION</code></td>
<td>The version of STLPort in use by default.</td>
<td><code>4.5.3</code></td>
<td>Other values can be selected in parallel setting the <a href=
"build_system.htm#initiating">build property</a>
&lt;stlport-version&gt; to values from the list of
<code>$(STLPORT_VERSIONS)</code></td>
</tr>
<tr>
<td><code>STLPORT_VERSIONS</code></td>
<td>A space-separated list of alternate versions of STLport available
on this machine.</td>
<td><code>4.5&nbsp;4.0</code></td>
</tr>
</table>
<h2><a name="features" id="features">Toolset-Specific Features</a></h2>The
following <code>msvc-stlport</code>-specific <a href=
"build_system.htm#features">features</a> can be used in target build
requirements or in the <a href=
"build_system.htm#initiating"><code>BUILD</code></a> variable:
<table border="1" summary="features">
<tr>
<th>Feature</th>
<th>Values</th>
<th>Default</th>
<th>Semantics</th>
</tr>
<tr>
<td><code>stlport-iostream</code></td>
<td><code>off on</code></td>
<td><code>off</code></td>
<td>Controls whether STLPort's own iostreams are in use. Though this
setting is <code>off</code> by default to save users from having to
build STLPort, we strongly recommend <code>on</code> instead.</td>
</tr>
<tr>
<td><code>stlport-version</code></td>
<td><code>$(STLPORT_VERSION)&nbsp;$(STLPORT_VERSIONS)</code> (see
above)</td>
<td><code>$(STLPORT_VERSION)</code></td>
<td>Selects a version of STLPort for each target</td>
</tr>
<tr>
<td><code>stlport-cstd-namespace</code></td>
<td><code>std global</code></td>
<td><code>std</code></td>
<td>Controls whether or not names from the "C" library headers such as
&lt;cstdlib&gt; are imported into <code>namespace std</code>.</td>
</tr>
</table>
<p>In addition to what this toolset provides, configuration and extended
functionality is available through the common <a href=
"stlport.html">stlport library support</a>.</p>
<hr>
<p>Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
14 May, 2002 <!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Revised $Date$</p>
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p>Copyright &copy; Dave Abrahams 2002, Rene Rivera 2005.</p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or

4
v1/python.jam
View File

@@ -82,6 +82,10 @@ else if $(UNIX)
{
PYTHON_EMBEDDED_LIBRARY = python$(PYTHON_VERSION) dl ;
}
else if $(OS) = OSF
{
PYTHON_EMBEDDED_LIBRARY = python$(PYTHON_VERSION) ;
}
else
{
PYTHON_EMBEDDED_LIBRARY = python$(PYTHON_VERSION) dl util ;

10
v1/qcc-tools.jam Normal file
View File

@@ -0,0 +1,10 @@
# Copyright (c) 2005 Rene Rivera.
# Distributed under the Boost Software License, Version 1.0.
# (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)
{
local GXX = QCC ;
local GCC = qcc ;
extends-toolset gcc ;
}

222
v1/stlport.html Normal file
View File

@@ -0,0 +1,222 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="../../../boost.css">
<title>Boost.Build - stlport library support</title>
</head>
<body link="#0000FF" vlink="#800080">
<table border="0" cellpadding="7" cellspacing="0" width="100%" summary=
"header">
<tbody>
<tr>
<td valign="top" width="300">
<h3><a href="http://www.boost.org/"><img height="86" width="277"
alt="C++ Boost" src="../../../boost.png" border="0"></a></h3>
</td>
<td valign="top">
<h1 align="center">Boost.Build</h1>
<h2 align="center">stlport library support</h2>
</td>
</tr>
</tbody>
</table>
<hr>
<h2>Introduction</h2>
<p>Boost.Build's <a href="stlport-tools.jam">stlport</a> supports the use
of <a href="http://www.stlport.org">STLport</a> standard library
implementation with the various Boost.Build toolsets. It is designed to
allow you to build and test with multiple installed versions of STLPort, so
that objects built in each configuration will be built into separate
directories. The configuration and features describe here are in addition
to those provided by the specific toolsets that can be configured use the
STLport library.</p>
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>
<p>The <code>stlport</code> support responds to the following variables,
which can be set in the environment or configured on the jam command-line
using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>.</p>
<p>In the table below, <i>version</i> corresponds to an STLPort version
number, e.g. "<code>5.0</code>".</p>
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
<th>Semantics</th>
<th>Default</th>
<th>Notes</th>
</tr>
<tr>
<td><code>STLPORT_PATH</code></td>
<td>A directory containing at least one subdirectory of the form
<code>/STLPort-</code><i>version</i> where an STLPort installation can
be found.</td>
<td><i>empty</i></td>
<td>Allows easy configuration for an installation where several STLPort
versions are installed under a single directory.</td>
</tr>
<tr>
<td><code>STLPORT_</code><i>version</i><code>_PATH</code></td>
<td>The directory where the specific STLPort <i>version</i>
installation can be found, in case there is no central location
appropriate for <code>STLPORT_PATH</code>, above, or a particular
version's installation is not located in the usual place.</td>
<td><i>empty</i></td>
<td>Allows configuration of a specific STLPort installation.</td>
</tr>
<tr>
<td><code>STLPORT_VERSION</code></td>
<td>The version of STLPort in use by default.</td>
<td><code>4.6.2</code></td>
<td>Other values can be selected in parallel setting the <a href=
"build_system.htm#initiating">build property</a>
&lt;stlport-version&gt; to values from the list of
<code>$(STLPORT_VERSIONS)</code></td>
</tr>
<tr>
<td><code>STLPORT_VERSIONS</code></td>
<td>A space-separated list of alternate versions of STLport available
on this machine.</td>
<td><code>5.0&nbsp;4.6.2&nbsp;4.6&nbsp;4.5.3&nbsp;4.5</code></td>
</tr>
</table>
<h2><a name="features" id="features">STLport Specific Features</a></h2>
<p>The following <code>stlport</code> specific <a href=
"build_system.htm#features">features</a> can be used in target build
requirements or in the <a href=
"build_system.htm#initiating"><code>BUILD</code></a> variable:</p>
<table border="1" summary="features">
<tr>
<th>Feature</th>
<th>Values</th>
<th>Default</th>
<th>Semantics</th>
</tr>
<tr>
<td><code>stlport-version</code></td>
<td><code>$(STLPORT_VERSION)&nbsp;$(STLPORT_VERSIONS)</code> (see
above)</td>
<td><code>$(STLPORT_VERSION)</code></td>
<td>Selects a version of STLPort for each target</td>
</tr>
<tr>
<td><code>stlport-iostream</code></td>
<td><code>on off</code></td>
<td><code>on</code></td>
<td>Controls whether STLPort's own iostreams are in use. The default
for this is now "on". This is because overwhelmingly STLport is used
for it's iostreams support to the extent that non-iostream mode is no
longer available on version 5.0. Since this mode is not available in
5.0 this feature is ignored when using version 5.0.</td>
</tr>
<tr>
<td><code>stlport-cstd-namespace</code></td>
<td><code>std global</code></td>
<td><code>std</code></td>
<td>Controls whether or not names from the "C" library headers such as
&lt;cstdlib&gt; are imported into <code>namespace std</code>.</td>
</tr>
<tr>
<td><code>stlport-debug-alloc</code></td>
<td><code>off on</code></td>
<td><code>off</code></td>
<td>Enables STLport support for debugging memory allocations, i.e. it
defines <code>_STLP_DEBUG_ALLOC</code> appropriately.</td>
</tr>
<tr>
<td><code>stlport-cross</code></td>
<td><code>off on</code></td>
<td><code>off</code></td>
<td>For STLport 5.0, with it's new library naming scheme, it is
possible to build using compiler specific targets. This tells
Boost.Build that you built STLport in it's "cross compile" mode and
will adjust how it looks for the STLport libraries to match.</td>
</tr>
<tr>
<td><code>stlport-extensions</code></td>
<td><code>on off</code></td>
<td><code>on</code></td>
<td>Defines <code>_STLP_NO_EXTENSIONS</code> appropriately.</td>
</tr>
<tr>
<td><code>stlport-anachronisms</code></td>
<td><code>on off</code></td>
<td><code>on</code></td>
<td>Defines <code>_STLP_NO_ANACHRONISMS</code> appropriately.</td>
</tr>
</table>
<hr>
<p>Revised $Date$</p>
<p>Copyright &copy; Dave Abrahams 2002, Aleksey Gurtovoy 2004, Rene Rivera
2005.</p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

120
v1/stlport.jam
View File

@@ -7,6 +7,8 @@
# Use this toolset to add STLport flavor for any base toolset
# define STLPORT_LIB_BASE_NAME to the shared between debug and release
# versions prefix for stlport library name for example stlport_sunpro
# Define STLPORT_AUTOLINK to use the autolink facilities of the new
# STLport-5.0
# STLport iostreams or native iostreams
feature stlport-iostream : on off ;
@@ -23,16 +25,20 @@ feature stlport-debug-alloc : off on ;
# ?
feature stlport-cstd-namespace : std global ;
# STLport-5 libraries are located in cross-compilation individual subdirectories.
feature stlport-cross : off on ;
CURR_TOOLSET = $(gCURRENT_TOOLSET) ;
# STLport versions
STLPORT_VERSION ?= 4.6.2 ;
STLPORT_VERSIONS ?= 4.6 4.5.3 4.5 ;
STLPORT_VERSIONS(default) ?= 4.6.2 ;
STLPORT_VERSIONS(4) ?= 4.6.2 4.6 4.5.3 4.5 ;
STLPORT_VERSIONS(5) ?= 5.0 ;
STLPORT_VERSION ?= $(STLPORT_VERSION(default)) ;
STLPORT_VERSIONS ?= $(STLPORT_VERSIONS(4)) $(STLPORT_VERSIONS(5)) ;
feature stlport-version : [ unique $(STLPORT_VERSION) $(STLPORT_VERSIONS) ] ;
flags $(CURR_TOOLSET) STLPORT_VERSION_RELEVANT_FEATURE <stlport-version> ;
STLPORT_LIB_DEBUG_SUFFIX ?= _stldebug ;
# singleton variables...
set-as-singleton STLPORT_INCLUDE_DIRECTORY STLPORT_LIB_DIRECTORY STLPORT_PATH STLPORT_ROOT ;
@@ -67,11 +73,11 @@ rule get-stlport-root
ECHO " found, in case there is no central location appropriate for STLPORT_PATH, above, or a" ;
ECHO " particular version's installation is not located in the usual place." ;
ECHO ;
ECHO STLPORT_VERSION - The version of STLport in use by default. Defaults to \"4.6\". Other ;
ECHO STLPORT_VERSION - The version of STLport in use by default. Defaults to \"$(STLPORT_VERSIONS(default))\". Other ;
ECHO " values can be selected in parallel setting the build property <stlport-version> to" ;
ECHO " values from the list of $(dollar)(STLPORT_VERSIONS)" ;
ECHO ;
ECHO STLPORT_VERSIONS - Alternate versions of STLport available on this machine. Defaults to \"4.6 4.5.3 4.5\". ;
ECHO STLPORT_VERSIONS - Alternate versions of STLport available on this machine. Defaults to $(STLPORT_VERSIONS:J=" ") . ;
ECHO ;
ECHO "Note that STLport iostreams are /not/ in use by default. To enable them, you must place" ;
ECHO " <stlport-iostream>on in your BUILD variable or in target requirements." ;
@@ -85,6 +91,8 @@ rule get-stlport-root
STLPORT_INCLUDE_DIRECTORY ?= stlport ;
STLPORT_LIB_DIRECTORY ?= lib ;
STLPORT_BIN_DIRECTORY ?= bin ;
STLPORT_LIB_DEBUG_SUFFIX ?= _stldebug ;
# Clear out the STD paths so that the real toolset doesn't include
# anything but the STLport as the STD. But also set the STDLIBPATH to
@@ -93,10 +101,10 @@ STLPORT_LIB_DIRECTORY ?= lib ;
local .stdlibpath = $(STDLIBPATH) ;
STDHDRS = ;
STDLIBPATH = ;
flags $(CURR_TOOLSET) STDHDRS : [ join [ get-stlport-root ] $(SLASH)$(STLPORT_INCLUDE_DIRECTORY) ] ;
flags $(CURR_TOOLSET) STDLIBPATH <stlport-iostream>on : [ join [ get-stlport-root ] $(SLASH)$(STLPORT_LIB_DIRECTORY) ] $(.stdlibpath) ;
flags $(CURR_TOOLSET) DEFINES <stlport-iostream>off : _STLP_NO_OWN_IOSTREAMS=1 _STLP_HAS_NO_NEW_IOSTREAMS=1 ;
### Common options.
flags $(CURR_TOOLSET) STDHDRS : [ join [ get-stlport-root ] $(SLASH)$(STLPORT_INCLUDE_DIRECTORY) ] ;
flags $(CURR_TOOLSET) DEFINES <stlport-extensions>off : _STLP_NO_EXTENSIONS=1 ;
flags $(CURR_TOOLSET) DEFINES <stlport-anachronisms>off : _STLP_NO_ANACHRONISMS=1 ;
flags $(CURR_TOOLSET) DEFINES <stlport-cstd-namespace>global : _STLP_VENDOR_GLOBAL_CSTD=1 ;
@@ -105,7 +113,93 @@ flags $(CURR_TOOLSET) DEFINES <stlport-debug-alloc>on : _STLP_DEBUG_ALLOC=1 ;
flags $(CURR_TOOLSET) DEFINES <runtime-build>debug : _STLP_DEBUG=1 _STLP_DEBUG_UNINITIALIZED=1 ;
flags $(CURR_TOOLSET) DEFINES <runtime-link>dynamic : _STLP_USE_DYNAMIC_LIB=1 ;
flags $(CURR_TOOLSET) FINDLIBS <stlport-iostream>on/<runtime-build>debug/<runtime-link>static : $(STLPORT_LIB_BASE_NAME)$(STLPORT_LIB_DEBUG_SUFFIX)$(STLPORT_LIB_STATIC_SUFFIX) ;
flags $(CURR_TOOLSET) FINDLIBS <stlport-iostream>on/<runtime-build>debug/<runtime-link>dynamic : $(STLPORT_LIB_BASE_NAME)$(STLPORT_LIB_DEBUG_SUFFIX) ;
flags $(CURR_TOOLSET) FINDLIBS <stlport-iostream>on/<runtime-build>release/<runtime-link>static : $(STLPORT_LIB_BASE_NAME)$(STLPORT_LIB_STATIC_SUFFIX) ;
flags $(CURR_TOOLSET) FINDLIBS <stlport-iostream>on/<runtime-build>release/<runtime-link>dynamic : $(STLPORT_LIB_BASE_NAME) ;
### STLport 4.x
flags $(CURR_TOOLSET) DEFINES
<stlport-version>$(STLPORT_VERSIONS(4))/<stlport-iostream>off :
_STLP_NO_OWN_IOSTREAMS=1 _STLP_HAS_NO_NEW_IOSTREAMS=1 ;
flags $(CURR_TOOLSET) STDLIBPATH
<stlport-version>$(STLPORT_VERSIONS(4))/<stlport-iostream>on :
[ join [ get-stlport-root ] $(SLASH)$(STLPORT_LIB_DIRECTORY) ]
$(.stdlibpath) ;
flags $(CURR_TOOLSET) FINDLIBS
<stlport-version>$(STLPORT_VERSIONS(4))/<stlport-iostream>on/<runtime-build>debug/<runtime-link>static :
$(STLPORT_LIB_BASE_NAME)$(STLPORT_LIB_DEBUG_SUFFIX)$(STLPORT_LIB_STATIC_SUFFIX) ;
flags $(CURR_TOOLSET) FINDLIBS
<stlport-version>$(STLPORT_VERSIONS(4))/<stlport-iostream>on/<runtime-build>debug/<runtime-link>dynamic :
$(STLPORT_LIB_BASE_NAME)$(STLPORT_LIB_DEBUG_SUFFIX) ;
flags $(CURR_TOOLSET) FINDLIBS
<stlport-version>$(STLPORT_VERSIONS(4))/<stlport-iostream>on/<runtime-build>release/<runtime-link>static :
$(STLPORT_LIB_BASE_NAME)$(STLPORT_LIB_STATIC_SUFFIX) ;
flags $(CURR_TOOLSET) FINDLIBS
<stlport-version>$(STLPORT_VERSIONS(4))/<stlport-iostream>on/<runtime-build>release/<runtime-link>dynamic :
$(STLPORT_LIB_BASE_NAME) ;
### STLport 5.x
switch $(CURR_TOOLSET)
{
case msvc* : STLPORT_AUTOLINK = TRUE ;
case vc* : STLPORT_AUTOLINK = TRUE ;
}
switch $(CURR_TOOLSET)
{
case intel-win32* : STLPORT_CROSS_DIR ?= icl ;
case iw* : STLPORT_CROSS_DIR ?= icl ;
case msvc* : STLPORT_CROSS_DIR ?= vc6 ;
case vc-6* : STLPORT_CROSS_DIR ?= vc6 ;
case vc-7-* : STLPORT_CROSS_DIR ?= vc70 ;
case vc-7_0* : STLPORT_CROSS_DIR ?= vc70 ;
case vc-7_1* : STLPORT_CROSS_DIR ?= vc71 ;
case vc-8* : STLPORT_CROSS_DIR ?= vc8 ;
}
switch $(CURR_TOOLSET)
{
# GCC compilers have 'g' to indicate debug.
case gcc* : STLPORT_DEBUG_SUFFIX ?= g ;
case mingw* : STLPORT_DEBUG_SUFFIX ?= g ;
case darwin* : STLPORT_DEBUG_SUFFIX ?= g ;
# The others use 'd'.
case * : STLPORT_DEBUG_SUFFIX ?= d ;
}
# STLport-5 doesn't directly support single-threaded builds. There is an open
# question if single-threaded application code can be combined with the
# multi-threaded STLport-5. Until that's answered this is commented out and
# boost-base.jam requires all builds to be multi-threaded.
#~ flags $(CURR_TOOLSET) DEFINES
#~ <stlport-version>$(STLPORT_VERSIONS(5)) :
#~ _STLP_THREADS=1 ;
flags $(CURR_TOOLSET) STDLIBPATH
<stlport-version>$(STLPORT_VERSIONS(5))/<stlport-cross>off :
[ join [ get-stlport-root ] $(SLASH)$(STLPORT_LIB_DIRECTORY) ]
[ join [ get-stlport-root ] $(SLASH)$(STLPORT_BIN_DIRECTORY) ]
$(.stdlibpath) ;
flags $(CURR_TOOLSET) STDLIBPATH
<stlport-version>$(STLPORT_VERSIONS(5))/<stlport-cross>on :
[ join [ get-stlport-root ] $(SLASH)$(STLPORT_LIB_DIRECTORY) $(SLASH)$(STLPORT_CROSS_DIR) ]
[ join [ get-stlport-root ] $(SLASH)$(STLPORT_BIN_DIRECTORY) $(SLASH)$(STLPORT_CROSS_DIR) ]
$(.stdlibpath) ;
if ! $(STLPORT_AUTOLINK)
{
STLPORT_LIB_STATIC_SUFFIX ?= "" ;
for local v in $(STLPORT_VERSIONS(5))
{
flags $(CURR_TOOLSET) FINDLIBS
<stlport-version>$(v)/<runtime-build>debug/<runtime-link>static :
stlportstl$(STLPORT_DEBUG_SUFFIX)$(STLPORT_LIB_STATIC_SUFFIX).$(v) ;
flags $(CURR_TOOLSET) FINDLIBS
<stlport-version>$(v)/<runtime-build>debug/<runtime-link>dynamic :
stlportstl$(STLPORT_DEBUG_SUFFIX).$(v) ;
flags $(CURR_TOOLSET) FINDLIBS
<stlport-version>$(v)/<runtime-build>release/<runtime-link>static :
stlport$(STLPORT_LIB_STATIC_SUFFIX).$(v) ;
flags $(CURR_TOOLSET) FINDLIBS
<stlport-version>$(v)/<runtime-build>release/<runtime-link>dynamic :
stlport.$(v) ;
}
}

129
v1/vc-7_1-stlport-tools.html
View File

@@ -3,8 +3,6 @@
<html>
<head>
<title>Boost.Build - vc-7_1-stlport toolset</title>
<meta name="generator" content=
"HTML Tidy for Linux/x86 (vers 1st September 2003), see www.w3.org">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="../../../boost.css">
</head>
@@ -31,94 +29,24 @@
<h2>Introduction</h2>
<p>Boost.Build's <a href=
"vc-7_1-stlport-tools.jam">vc-7_1-stlport</a> toolset supports the
Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual C++</a> .NET
2003 command-line tools, using the <a href=
"http://www.stlport.org">STLport</a> standard library implementation on
Microsoft Windows. It is designed to allow you to build and test with
multiple installed versions of STLPort, so that objects build in each
configuration will be built into separate directories.</p>
<p>Boost.Build's <a href="vc-7_1-stlport-tools.jam">vc-7_1-stlport</a>
toolset supports the Microsoft <a href=
"http://msdn.microsoft.com/visualc/">Visual C++</a> .NET 2003 command-line
tools, using the <a href="http://www.stlport.org">STLport</a> standard
library implementation on Microsoft Windows. It is designed to allow you to
build and test with multiple installed versions of STLPort, so that objects
build in each configuration will be built into separate directories.</p>
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The <code>vc-7_1-stlport</code> toolset responds to the
following variables, which can be set in the environment or configured on
the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. It is an extension of the
<a href="msvc-stlport-tools.html">msvc-stlport toolset</a> and therefore
responds to all of the MSVC <a href=
"msvc-tools.html#configuration">configuration variables</a> in addition to
those listed below.
<p>In the table below, <i>version</i> corresponds to an STLPort version
number, e.g. "<code>4.5.3</code>".</p>
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
<th>Semantics</th>
<th>Default</th>
<th>Notes</th>
</tr>
<tr>
<td><code>STLPORT_PATH</code></td>
<td>A directory containing at least one subdirectory of the form
<code>/STLPort-</code><i>version</i> where an STLPort installation can
be found.</td>
<td><i>empty</i></td>
<td>Allows easy configuration for an installation where several STLPort
versions are installed under a single directory.</td>
</tr>
<tr>
<td><code>STLPORT_</code><i>version</i><code>_PATH</code></td>
<td>The directory where the specific STLPort <i>version</i>
installation can be found, in case there is no central location
appropriate for <code>STLPORT_PATH</code>, above, or a particular
version's installation is not located in the usual place.</td>
<td><i>empty</i></td>
<td>Allows configuration of a specific STLPort installation.</td>
</tr>
<tr>
<td><code>STLPORT_VERSION</code></td>
<td>The version of STLPort in use by default.</td>
<td><code>4.6</code></td>
<td>Other values can be selected in parallel setting the <a href=
"build_system.htm#initiating">build property</a>
&lt;stlport-version&gt; to values from the list of
<code>$(STLPORT_VERSIONS)</code></td>
</tr>
<tr>
<td><code>STLPORT_VERSIONS</code></td>
<td>A space-separated list of alternate versions of STLport available
on this machine.</td>
<td><code>4.6 4.5&nbsp;4.0</code></td>
</tr>
</table>
<p>In addition to what this toolset provides, configuration and extended
functionality is available through the common <a href=
"stlport.html">stlport library support</a>.</p>
<h2><a name="features" id="features">Toolset-Specific Features</a></h2>
<p>The following <code>vc-7_1-stlport</code>-specific <a href=
"build_system.htm#features">features</a> can be used in target build
requirements or in the <a href=
"build_system.htm#initiating"><code>BUILD</code></a> variable:
</p>
"build_system.htm#initiating"><code>BUILD</code></a> variable:</p>
<table border="1" summary="features">
<tr>
@@ -143,40 +71,13 @@
Turning this on may result in unresolved externals from STLPort, unless
you rebuild STLPort with /Zc:wchar_t.</td>
</tr>
<tr>
<td><code>stlport-version</code></td>
<td><code>$(STLPORT_VERSION)&nbsp;$(STLPORT_VERSIONS)</code> (see
above)</td>
<td><code>$(STLPORT_VERSION)</code></td>
<td>Selects a version of STLPort for each target</td>
</tr>
<tr>
<td><code>stlport-cstd-namespace</code></td>
<td><code>std global</code></td>
<td><code>std</code></td>
<td>Controls whether or not names from the "C" library headers such as
&lt;cstdlib&gt; are imported into <code>namespace std</code>.</td>
</tr>
</table>
<hr>
<p>Revised&nbsp;&nbsp;
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
10 Oct&nbsp;2004&nbsp;
<!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Revised $Date$</p>
<p>
Copyright &copy; Dave Abrahams 2002.<br>
Copyright &copy; John Maddock 2003.
</p>
<p>Copyright &copy; Dave Abrahams 2002, John Maddock 2003, Rene Rivera
2005.</p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or

109
v1/vc7-stlport-tools.html
View File

@@ -3,8 +3,6 @@
<html>
<head>
<title>Boost.Build - msvc-stlport toolset</title>
<meta name="generator" content=
"HTML Tidy for Linux/x86 (vers 1st September 2003), see www.w3.org">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="../../../boost.css">
</head>
@@ -40,78 +38,9 @@
that objects build in each configuration will be built into separate
directories.</p>
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The <code>vc7-stlport</code> toolset responds to the
following variables, which can be set in the environment or configured on
the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. It is an extension of the
<a href="msvc-stlport-tools.html">msvc-stlport toolset</a> and therefore
responds to all of the MSVC <a href=
"msvc-tools.html#configuration">configuration variables</a> in addition to
those listed below.
<p>In the table below, <i>version</i> corresponds to an STLPort version
number, e.g. "<code>4.5.3</code>".</p>
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
<th>Semantics</th>
<th>Default</th>
<th>Notes</th>
</tr>
<tr>
<td><code>STLPORT_PATH</code></td>
<td>A directory containing at least one subdirectory of the form
<code>/STLPort-</code><i>version</i> where an STLPort installation can
be found.</td>
<td><i>empty</i></td>
<td>Allows easy configuration for an installation where several STLPort
versions are installed under a single directory.</td>
</tr>
<tr>
<td><code>STLPORT_</code><i>version</i><code>_PATH</code></td>
<td>The directory where the specific STLPort <i>version</i>
installation can be found, in case there is no central location
appropriate for <code>STLPORT_PATH</code>, above, or a particular
version's installation is not located in the usual place.</td>
<td><i>empty</i></td>
<td>Allows configuration of a specific STLPort installation.</td>
</tr>
<tr>
<td><code>STLPORT_VERSION</code></td>
<td>The version of STLPort in use by default.</td>
<td><code>4.6</code></td>
<td>Other values can be selected in parallel setting the <a href=
"build_system.htm#initiating">build property</a>
&lt;stlport-version&gt; to values from the list of
<code>$(STLPORT_VERSIONS)</code></td>
</tr>
<tr>
<td><code>STLPORT_VERSIONS</code></td>
<td>A space-separated list of alternate versions of STLport available
on this machine.</td>
<td><code>4.6 4.5&nbsp;4.0</code></td>
</tr>
</table>
<p>In addition to what this toolset provides, configuration and extended
functionality is available through the common <a href=
"stlport.html">stlport library support</a>.</p>
<h2><a name="features" id="features">Toolset-Specific Features</a></h2>The
following vc7 <code>-stlport</code>-specific <a href=
@@ -142,39 +71,13 @@
Turning this on may result in unresolved externals from STLPort, unless
you rebuild STLPort with /Zc:wchar_t.</td>
</tr>
<tr>
<td><code>stlport-version</code></td>
<td><code>$(STLPORT_VERSION)&nbsp;$(STLPORT_VERSIONS)</code> (see
above)</td>
<td><code>$(STLPORT_VERSION)</code></td>
<td>Selects a version of STLPort for each target</td>
</tr>
<tr>
<td><code>stlport-cstd-namespace</code></td>
<td><code>std global</code></td>
<td><code>std</code></td>
<td>Controls whether or not names from the "C" library headers such as
&lt;cstdlib&gt; are imported into <code>namespace std</code>.</td>
</tr>
</table>
<hr>
<p>Revised&nbsp;&nbsp;
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
24 Dec&nbsp;2003&nbsp;
<!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Revised $Date$</p>
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p>Copyright &copy; John Maddock 2003.</p>
<p>Copyright &copy; Dave Abrahams 2002, John Maddock 2003, Rene Rivera
2005.</p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or