Planet
navi homePPSaboutscreenshotsdownloaddevelopmentforum

source: downloads/boost_1_33_1/tools/build/v1/stlport.html @ 12

Last change on this file since 12 was 12, checked in by landauf, 17 years ago

added boost
File size: 6.4 KB
Line 
1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2
3<html>
4<head>
5  <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
6  <link rel="stylesheet" type="text/css" href="../../../boost.css">
7
8  <title>Boost.Build - stlport library support</title>
9</head>
10
11<body link="#0000FF" vlink="#800080">
12  <table border="0" cellpadding="7" cellspacing="0" width="100%" summary=
13  "header">
14    <tbody>
15      <tr>
16        <td valign="top" width="300">
17          <h3><a href="http://www.boost.org/"><img height="86" width="277"
18          alt="C++ Boost" src="../../../boost.png" border="0"></a></h3>
19        </td>
20
21        <td valign="top">
22          <h1 align="center">Boost.Build</h1>
23
24          <h2 align="center">stlport library support</h2>
25        </td>
26      </tr>
27    </tbody>
28  </table>
29  <hr>
30
31  <h2>Introduction</h2>
32
33  <p>Boost.Build's <a href="stlport.jam">stlport</a> supports the use
34  of <a href="http://www.stlport.org">STLport</a> standard library
35  implementation with the various Boost.Build toolsets. It is designed to
36  allow you to build and test with multiple installed versions of STLPort, so
37  that objects built in each configuration will be built into separate
38  directories. The configuration and features describe here are in addition
39  to those provided by the specific toolsets that can be configured use the
40  STLport library.</p>
41
42  <h2><a name="configuration" id="configuration">Configuration
43  Variables</a></h2>
44
45  <p>The <code>stlport</code> support responds to the following variables,
46  which can be set in the environment or configured on the jam command-line
47  using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>.</p>
48
49  <p>In the table below, <i>version</i> corresponds to an STLPort version
50  number, e.g. "<code>5.0</code>".</p>
51
52  <table border="1" summary="settings">
53    <tr>
54      <th>Variable Name</th>
55
56      <th>Semantics</th>
57
58      <th>Default</th>
59
60      <th>Notes</th>
61    </tr>
62
63    <tr>
64      <td><code>STLPORT_PATH</code></td>
65
66      <td>A directory containing at least one subdirectory of the form
67      <code>/STLPort-</code><i>version</i> where an STLPort installation can
68      be found.</td>
69
70      <td><i>empty</i></td>
71
72      <td>Allows easy configuration for an installation where several STLPort
73      versions are installed under a single directory.</td>
74    </tr>
75
76    <tr>
77      <td><code>STLPORT_</code><i>version</i><code>_PATH</code></td>
78
79      <td>The directory where the specific STLPort <i>version</i>
80      installation can be found, in case there is no central location
81      appropriate for <code>STLPORT_PATH</code>, above, or a particular
82      version's installation is not located in the usual place.</td>
83
84      <td><i>empty</i></td>
85
86      <td>Allows configuration of a specific STLPort installation.</td>
87    </tr>
88
89    <tr>
90      <td><code>STLPORT_VERSION</code></td>
91
92      <td>The version of STLPort in use by default.</td>
93
94      <td><code>4.6.2</code></td>
95
96      <td>Other values can be selected in parallel setting the <a href=
97      "build_system.htm#initiating">build property</a>
98      &lt;stlport-version&gt; to values from the list of
99      <code>$(STLPORT_VERSIONS)</code></td>
100    </tr>
101
102    <tr>
103      <td><code>STLPORT_VERSIONS</code></td>
104
105      <td>A space-separated list of alternate versions of STLport available
106      on this machine.</td>
107
108      <td><code>5.0&nbsp;4.6.2&nbsp;4.6&nbsp;4.5.3&nbsp;4.5</code></td>
109    </tr>
110  </table>
111
112  <h2><a name="features" id="features">STLport Specific Features</a></h2>
113
114  <p>The following <code>stlport</code> specific <a href=
115  "build_system.htm#features">features</a> can be used in target build
116  requirements or in the <a href=
117  "build_system.htm#initiating"><code>BUILD</code></a> variable:</p>
118
119  <table border="1" summary="features">
120    <tr>
121      <th>Feature</th>
122
123      <th>Values</th>
124
125      <th>Default</th>
126
127      <th>Semantics</th>
128    </tr>
129
130    <tr>
131      <td><code>stlport-version</code></td>
132
133      <td><code>$(STLPORT_VERSION)&nbsp;$(STLPORT_VERSIONS)</code> (see
134      above)</td>
135
136      <td><code>$(STLPORT_VERSION)</code></td>
137
138      <td>Selects a version of STLPort for each target</td>
139    </tr>
140
141    <tr>
142      <td><code>stlport-iostream</code></td>
143
144      <td><code>on off</code></td>
145
146      <td><code>on</code></td>
147
148      <td>Controls whether STLPort's own iostreams are in use. The default
149      for this is now "on". This is because overwhelmingly STLport is used
150      for it's iostreams support to the extent that non-iostream mode is no
151      longer available on version 5.0. Since this mode is not available in
152      5.0 this feature is ignored when using version 5.0.</td>
153    </tr>
154
155    <tr>
156      <td><code>stlport-cstd-namespace</code></td>
157
158      <td><code>std global</code></td>
159
160      <td><code>std</code></td>
161
162      <td>Controls whether or not names from the "C" library headers such as
163      &lt;cstdlib&gt; are imported into <code>namespace std</code>.</td>
164    </tr>
165
166    <tr>
167      <td><code>stlport-debug-alloc</code></td>
168
169      <td><code>off on</code></td>
170
171      <td><code>off</code></td>
172
173      <td>Enables STLport support for debugging memory allocations, i.e. it
174      defines <code>_STLP_DEBUG_ALLOC</code> appropriately.</td>
175    </tr>
176
177    <tr>
178      <td><code>stlport-cross</code></td>
179
180      <td><code>off on</code></td>
181
182      <td><code>off</code></td>
183
184      <td>For STLport 5.0, with it's new library naming scheme, it is
185      possible to build using compiler specific targets. This tells
186      Boost.Build that you built STLport in it's "cross compile" mode and
187      will adjust how it looks for the STLport libraries to match.</td>
188    </tr>
189
190    <tr>
191      <td><code>stlport-extensions</code></td>
192
193      <td><code>on off</code></td>
194
195      <td><code>on</code></td>
196
197      <td>Defines <code>_STLP_NO_EXTENSIONS</code> appropriately.</td>
198    </tr>
199
200    <tr>
201      <td><code>stlport-anachronisms</code></td>
202
203      <td><code>on off</code></td>
204
205      <td><code>on</code></td>
206
207      <td>Defines <code>_STLP_NO_ANACHRONISMS</code> appropriately.</td>
208    </tr>
209  </table>
210  <hr>
211
212  <p>Revised $Date: 2005/12/01 04:52:04 $</p>
213
214  <p>Copyright &copy; Dave Abrahams 2002, Aleksey Gurtovoy 2004, Rene Rivera
215  2005.</p>
216
217  <p><small>Distributed under the Boost Software License, Version 1.0. (See
218  accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
219  copy at <a href=
220  "http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
221</body>
222</html>
Note: See TracBrowser for help on using the repository browser.