Planet
navi homePPSaboutscreenshotsdownloaddevelopmentforum

source: downloads/boost_1_34_1/doc/html/jam/building.html @ 29

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

updated boost from 1_33_1 to 1_34_1
File size: 14.4 KB
Line 
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title> Building BJam</title>
5<link rel="stylesheet" href="../boostbook.css" type="text/css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.68.1">
7<link rel="start" href="../index.html" title="The Boost C++ Libraries BoostBook Documentation Subset">
8<link rel="up" href="../jam.html" title="Chapter 24. Boost.Jam : 3.1.14">
9<link rel="prev" href="../jam.html" title="Chapter 24. Boost.Jam : 3.1.14">
10<link rel="next" href="usage.html" title=" Using BJam">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
13<table cellpadding="2" width="100%">
14<td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../boost.png"></td>
15<td align="center"><a href="../../../index.htm">Home</a></td>
16<td align="center"><a href="../../../libs/libraries.htm">Libraries</a></td>
17<td align="center"><a href="../../../people/people.htm">People</a></td>
18<td align="center"><a href="../../../more/faq.htm">FAQ</a></td>
19<td align="center"><a href="../../../more/index.htm">More</a></td>
20</table>
21<hr>
22<div class="spirit-nav">
23<a accesskey="p" href="../jam.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../jam.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="usage.html"><img src="../images/next.png" alt="Next"></a>
24</div>
25<div class="section" lang="en">
26<div class="titlepage"><div><div><h2 class="title" style="clear: both">
27<a name="jam.building"></a> Building BJam</h2></div></div></div>
28<p>
29      Installing <code class="literal">BJam</code> after building it is simply a matter of
30      copying the generated executables someplace in your <code class="literal">PATH</code>.
31      For building the executables there are a set of <code class="literal">build</code> bootstrap
32      scripts to accomodate particular environments. The scripts take one optional
33      argument, the name of the toolset to build with. When the toolset is not given
34      an attempt is made to detect an available toolset and use that. The build scripts
35      accept these arguments:
36    </p>
37<pre class="programlisting"><span class="emphasis"><em>build</em></span> [<span class="emphasis"><em>toolset</em></span>]
38</pre>
39<p>
40      Running the scripts without arguments will give you the best chance of success.
41      On Windows platforms from a command console do:
42    </p>
43<pre class="programlisting">cd <span class="emphasis"><em>jam source location</em></span>
44.\build.bat
45</pre>
46<p>
47      On Unix type platforms do:
48    </p>
49<pre class="programlisting">cd <span class="emphasis"><em>jam source location</em></span>
50sh ./build.sh
51</pre>
52<p>
53      For the Boost.Jam source included with the Boost distribution the <span class="emphasis"><em>jam
54      source location</em></span> is <code class="literal">BOOST_ROOT/tools/jam/src</code>.
55    </p>
56<p>
57      If the scripts fail to detect an appropriate toolset to build with your particular
58      toolset may not be auto-detectable. In that case, you can specify the toolset
59      as the first argument, this assumes that the toolset is readily available in
60      the <code class="literal">PATH</code>.
61    </p>
62<div class="note"><table border="0" summary="Note">
63<tr>
64<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
65<th align="left">Note</th>
66</tr>
67<tr><td align="left" valign="top"><p>
68        The toolset used to build Boost.Jam is independent of the toolsets used for
69        Boost.Build. Only one version of Boost.Jam is needed to use Boost.Build.
70      </p></td></tr>
71</table></div>
72<p>
73      The supported toolsets, and wether they are auto-detected, are:
74    </p>
75<div class="informaltable">
76<h4>
77<a name="id2092074"></a>
78        <span class="table-title">Supported Toolsets</span>
79      </h4>
80<table class="table">
81<colgroup>
82<col>
83<col>
84<col>
85<col>
86</colgroup>
87<thead><tr>
88<th>Script</th>
89<th>Platform</th>
90<th>Toolset</th>
91<th>Detection</th>
92</tr></thead>
93<tbody>
94<tr>
95<td><code class="literal">build.bat</code></td>
96<td>Windows NT, 2000, and
97            XP</td>
98<td> <a href="http://www.borland.com/bcppbuilder/freecompiler" target="_top"><code class="literal">borland</code></a><br>
99            <a href="http://www.borland.com/" target="_top">Borland</a> C++Builder (BCC
100            5.5)</td>
101<td> * Common install location: "<code class="literal">C:\Borland\BCC55</code>"<br>
102            * <code class="literal">BCC32.EXE</code> in <code class="literal">PATH</code> </td>
103</tr>
104<tr>
105<td> </td>
106<td> </td>
107<td> <a href="http://www.comeaucomputing.com/" target="_top"><code class="literal">como</code></a><br>
108            Comeau Computing C/C++</td>
109<td> </td>
110</tr>
111<tr>
112<td> </td>
113<td> </td>
114<td> <a href="http://gcc.gnu.org/" target="_top"><code class="literal">gcc</code></a><br>
115            GNU GCC</td>
116<td> </td>
117</tr>
118<tr>
119<td> </td>
120<td> </td>
121<td> <a href="http://gcc.gnu.org/" target="_top"><code class="literal">gcc-nocygwin</code></a><br>
122            GNU GCC</td>
123<td> </td>
124</tr>
125<tr>
126<td> </td>
127<td> </td>
128<td> <a href="http://www.intel.com/software/products/compilers/c60" target="_top"><code class="literal">intel-win32</code></a><br>
129            Intel C++ Compiler for Windows</td>
130<td> * <code class="literal">ICL.EXE</code>
131            in <code class="literal">PATH</code> </td>
132</tr>
133<tr>
134<td> </td>
135<td> </td>
136<td> <a href="http://www.metrowerks.com/" target="_top"><code class="literal">metrowerks</code></a><br>
137            MetroWerks CodeWarrior C/C++ 7.x, 8.x, 9.x</td>
138<td> * <code class="literal">CWFolder</code>
139            variable configured * <code class="literal">MWCC.EXE</code> in <code class="literal">PATH</code>
140            </td>
141</tr>
142<tr>
143<td> </td>
144<td> </td>
145<td> <a href="http://www.mingw.org/" target="_top"><code class="literal">mingw</code></a><br>
146            GNU <a href="http://gcc.gnu.org/" target="_top">GCC</a> as the <a href="http://www.mingw.org/" target="_top">MinGW</a>
147            configuration</td>
148<td> * Common install location: "<code class="literal">C:\MinGW</code>"
149            </td>
150</tr>
151<tr>
152<td> </td>
153<td> </td>
154<td> <a href="http://msdn.microsoft.com/visualc/" target="_top"><code class="literal">msvc</code></a><br>
155            Microsoft Visual C++ 6.x</td>
156<td> * <code class="literal">VCVARS32.BAT</code>
157            already configured<br> * <code class="literal">%MSVCDir%</code> is present in
158            environment<br> * Common install locations: "<code class="literal">%ProgramFiles%\Microsoft
159            Visual Studio</code>", "<code class="literal">%ProgramFiles%\Microsoft
160            Visual C++</code>"<br> * <code class="literal">CL.EXE</code> in <code class="literal">PATH</code><br>
161            * <code class="literal">VCVARS32.BAT</code> in <code class="literal">PATH</code> </td>
162</tr>
163<tr>
164<td> </td>
165<td> </td>
166<td> <a href="http://msdn.microsoft.com/visualc/" target="_top"><code class="literal">vc7</code></a><br>
167            Microsoft Visual C++ 7.x</td>
168<td> * <code class="literal">VCVARS32.BAT</code>
169            or <code class="literal">VSVARS32.BAT</code> already configured * <code class="literal">%VS71COMNTOOLS%</code>
170            is present in environment<br> * <code class="literal">%VCINSTALLDIR%</code> is
171            present in environment<br> * Common install locations: "<code class="literal">%ProgramFiles%\Microsoft
172            Visual Studio .NET</code>", "<code class="literal">%ProgramFiles%\Microsoft
173            Visual Studio .NET 2003</code>"<br> * <code class="literal">CL.EXE</code>
174            in <code class="literal">PATH</code><br> * <code class="literal">VCVARS32.BAT</code> in
175            <code class="literal">PATH</code> </td>
176</tr>
177<tr>
178<td> </td>
179<td> </td>
180<td> <a href="http://msdn.microsoft.com/visualc/" target="_top"><code class="literal">vc8</code></a><br>
181            Microsoft Visual C++ 8.x</td>
182<td> * <code class="literal">VCVARS32.BAT</code>
183            or <code class="literal">VSVARS32.BAT</code> already configured<br> * <code class="literal">%VS80COMNTOOLS%</code>
184            is present in environment<br> * Common install location: "<code class="literal">%ProgramFiles%\Microsoft
185            Visual Studio 8</code>"<br> * <code class="literal">CL.EXE</code> in
186            <code class="literal">PATH</code><br> * <code class="literal">VCVARS32.BAT</code> in <code class="literal">PATH</code>
187            </td>
188</tr>
189<tr>
190<td><code class="literal">build.sh</code></td>
191<td>Unix, Linux, Cygwin,
192            etc.</td>
193<td> <a href="http://www.hp.com/go/c++" target="_top"><code class="literal">acc</code></a><br>
194            HP-UX aCC</td>
195<td> * <code class="literal">aCC</code> in <code class="literal">PATH</code><br>
196            * <code class="literal">uname</code> is "HP-UX" </td>
197</tr>
198<tr>
199<td> </td>
200<td> </td>
201<td> <a href="http://www.comeaucomputing.com/" target="_top"><code class="literal">como</code></a><br>
202            Comeau Computing C/C++</td>
203<td> * como in <code class="literal">PATH</code>
204            </td>
205</tr>
206<tr>
207<td> </td>
208<td> </td>
209<td> <a href="http://gcc.gnu.org/" target="_top"><code class="literal">gcc</code></a><br>
210            GNU GCC</td>
211<td> * gcc in <code class="literal">PATH</code> </td>
212</tr>
213<tr>
214<td> </td>
215<td> </td>
216<td> <a href="http://www.intel.com/software/products/compilers/c60l/" target="_top"><code class="literal">intel-linux</code></a><br>
217            Intel C++ for Linux</td>
218<td> * <code class="literal">icc</code> in <code class="literal">PATH</code><br>
219            * Common install locations: "<code class="literal">/opt/intel/cc/9.0</code>",
220            "<code class="literal">/opt/intel_cc_80</code>", "<code class="literal">/opt/intel/compiler70</code>",
221            "<code class="literal">/opt/intel/compiler60</code>", "<code class="literal">/opt/intel/compiler50</code>"
222            </td>
223</tr>
224<tr>
225<td> </td>
226<td> </td>
227<td> <code class="literal">kcc</code><br>
228            Intel KAI C++</td>
229<td> * <code class="literal">KCC</code> in <code class="literal">PATH</code>
230            </td>
231</tr>
232<tr>
233<td> </td>
234<td> </td>
235<td> <a href="http://www.borland.com/bcppbuilder/freecompiler" target="_top"><code class="literal">kylix</code></a><br>
236            <a href="http://www.borland.com/" target="_top">Borland</a> C++Builder</td>
237<td>
238            * bc++ in PATH </td>
239</tr>
240<tr>
241<td> </td>
242<td> </td>
243<td> <a href="http://www.sgi.com/developers/devtools/languages/mipspro.html" target="_top"><code class="literal">mipspro</code></a><br>
244            SGI MIPSpro C</td>
245<td> * <code class="literal">uname</code> is "<code class="literal">IRIX</code>"
246            or "<code class="literal">IRIX64</code>" </td>
247</tr>
248<tr>
249<td> </td>
250<td> </td>
251<td> <code class="literal">sunpro</code><br>
252            Sun Workshop 6 C++</td>
253<td> * Standard install location: "<code class="literal">/opt/SUNWspro</code>"
254            </td>
255</tr>
256<tr>
257<td> </td>
258<td> </td>
259<td> <code class="literal">qcc</code><br>
260            <a href="http://www.qnx.com/" target="_top">QNX Neutrino</a>
261</td>
262<td>
263            * <code class="literal">uname</code> is "<code class="literal">QNX</code>" and
264            <code class="literal">qcc</code> in <code class="literal">PATH</code> </td>
265</tr>
266<tr>
267<td> </td>
268<td> </td>
269<td> <a href="http://www.tru64unix.compaq.com/cplus/" target="_top"><code class="literal">true64cxx</code></a><br>
270            Compaq C++ Compiler for True64 UNIX</td>
271<td> * <code class="literal">uname</code>
272            is "<code class="literal">OSF1</code>" </td>
273</tr>
274<tr>
275<td> </td>
276<td> </td>
277<td> <a href="http://www-3.ibm.com/software/ad/vacpp/" target="_top"><code class="literal">vacpp</code></a><br>
278            IBM VisualAge C++</td>
279<td> * <code class="literal">xlc</code> in <code class="literal">PATH</code>
280            </td>
281</tr>
282<tr>
283<td> </td>
284<td>MacOS X</td>
285<td> <a href="http://developer.apple.com/tools/compilers.html" target="_top"><code class="literal">darwin</code></a><br>
286            Apple MacOS X GCC</td>
287<td> * <code class="literal">uname</code> is "<code class="literal">Darwin</code>"
288            </td>
289</tr>
290<tr>
291<td> </td>
292<td>Windows NT, 2000, and XP</td>
293<td> <a href="http://www.mingw.org/" target="_top"><code class="literal">mingw</code></a><br> GNU
294            <a href="http://gcc.gnu.org/" target="_top">GCC</a> as the <a href="http://www.mingw.org/" target="_top">MinGW</a>
295            configuration with the MSYS shell</td>
296<td> * Common install location:
297            "<code class="literal">/mingw</code>" </td>
298</tr>
299</tbody>
300</table>
301</div>
302<p>
303      The built executables are placed in a subdirectory specific to your platform.
304      For example, in Linux running on an Intel x86 compatible chip, the executables
305      are placed in: "<code class="literal">bin.linuxx86</code>". The <code class="literal">bjam[.exe]</code>
306      executable can be used to invoke Boost.Build.
307    </p>
308<p>
309      The build scripts support additional invocation arguments for use by developers
310      of Boost.Jam. The extra arguments come after the toolset, and can take the
311      form of "<code class="literal">--option</code>" or targets for the <code class="literal">build.jam</code>
312      script:
313    </p>
314<pre class="programlisting"><span class="emphasis"><em>build</em></span> [<span class="emphasis"><em>toolset</em></span>] [--<span class="emphasis"><em>option</em></span>+ <span class="emphasis"><em>target</em></span>*]
315</pre>
316<p>
317      There is currently only one available option, "<code class="literal">--debug</code>",
318      which builds debugging versions of the executable. When built they are placed
319      in their own directory "<code class="literal">bin./platform/.debug</code>".
320      To specify targets without options, one can suply a special ignore option "<code class="literal">---</code>".
321    </p>
322<p>
323      Currently there are two targets supported: <code class="literal">dist</code>, and <code class="literal">clean</code>.
324      Respectively they: generate packages (compressed archives) as appropriate for
325      distribution in the platform, or remove all the built executables and objects.
326    </p>
327</div>
328<table width="100%"><tr>
329<td align="left"></td>
330<td align="right"><small>Copyright © 2003-2006 Rene
331      Rivera, David Abrahams, Vladimir Prus</small></td>
332</tr></table>
333<hr>
334<div class="spirit-nav">
335<a accesskey="p" href="../jam.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../jam.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="usage.html"><img src="../images/next.png" alt="Next"></a>
336</div>
337</body>
338</html>
Note: See TracBrowser for help on using the repository browser.