mirror of
https://github.com/boostorg/build.git
synced 2026-02-14 00:32:11 +00:00
Clarify installation docs, using suggestions from Ansgar Philippsen.
[SVN r18307]
This commit is contained in:
@@ -22,12 +22,12 @@
|
||||
div.alert { color: red }
|
||||
table { align: center; border: thin; }
|
||||
|
||||
</style>
|
||||
</style>
|
||||
</head>
|
||||
<!-- Things yet to document:
|
||||
- build request, build request expansion and directly requested targets
|
||||
- conditional properties
|
||||
-->
|
||||
- build request, build request expansion and directly requested targets
|
||||
- conditional properties
|
||||
-->
|
||||
|
||||
<body>
|
||||
<p><a href="../../index.htm"><img class="banner" height="86" width="277"
|
||||
@@ -111,24 +111,31 @@
|
||||
"jam_src/index.html">Boost.Jam documentation</a> has more details in
|
||||
case you need them.</li>
|
||||
|
||||
<li>Place the Boost.Jam binary, called "bjam" or "bjam.exe", somewhere
|
||||
in your <tt>PATH</tt>.</li>
|
||||
|
||||
<li style="list-style: none">After that, you can go to "examples-v2"
|
||||
directory and run <tt>bjam --version</tt>.</li>
|
||||
|
||||
<li>
|
||||
Configure toolsets to use. Open <tt>new/user-config.jam</tt> file and
|
||||
follow instructions there to specify what compiles/libraries you have
|
||||
and where they are located. After that, you should be able to go to
|
||||
<tt>examples-v2/hello</tt>, and run <tt>bjam</tt> there. A simple
|
||||
application will be built. You can also play with other projects in
|
||||
<tt>examples-v2</tt>.
|
||||
Place the Boost.Jam binary, called "bjam" or "bjam.exe", somewhere in
|
||||
your <tt>PATH</tt>. Verify that correct bjam is being executed by
|
||||
running "bjam --version". You should get
|
||||
<pre>
|
||||
Boost.Build V2 (Milestone N)
|
||||
|
||||
</pre>
|
||||
(where N is the version you've downloaded).
|
||||
</li>
|
||||
|
||||
<p>It is slighly better way is to copy <tt>new/user-config.jam</tt>
|
||||
into one of the locations where it can be found (given in <a href=
|
||||
"#config_files_location">this table</a>). This prevent you from
|
||||
accidentally overwriting your config when updating.</p>
|
||||
<li>Configure toolsets to use. Open <tt>new/user-config.jam</tt> file
|
||||
and follow instructions there to specify what compiles/libraries you
|
||||
have and where they are located.</li>
|
||||
|
||||
<li>You should now be able to go to <tt>examples-v2/hello</tt>, and run
|
||||
<tt>bjam</tt> there. A simple application will be built. You can also
|
||||
play with other projects in <tt>examples-v2</tt>.
|
||||
<!-- This part should not go into intoduction docs, but we need to place
|
||||
it somewhere.
|
||||
|
||||
<p>It is slighly better way is to copy <tt>new/user-config.jam</tt>
|
||||
into one of the locations where it can be found (given in <a href=
|
||||
"#config_files_location">this table</a>). This prevent you from
|
||||
accidentally overwriting your config when updating.</p> -->
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
@@ -1691,7 +1698,6 @@ borland/runtime-link=static,dynamic
|
||||
notice appears in all copies. This document is provided ``as is'' without
|
||||
express or implied warranty, and with no claim as to its suitability for
|
||||
any purpose.</p>
|
||||
|
||||
<!-- sf logo -->
|
||||
</body>
|
||||
</html>
|
||||
|
||||
Reference in New Issue
Block a user