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

Clarify instructions for installing from CVS.

Browse Source 
[SVN r19850]
This commit is contained in:
Vladimir Prus
2003-08-29 07:17:18 +00:00
parent c773394947
commit d95e8638c1
2 changed files with 60 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files

55
boost_build_v2.html
View File

@@ -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"
@@ -145,11 +145,10 @@
<hr>
<h2 id="installation">Installation</h2>
Assuming you're installing Boost.Build from sources, the following steps
are needed. All paths are given relatively to Boost.Build root directory,
which is the directory with the document you are reading. When using
Boost distribution, Boost.Build root is located at
<tt>$boost_root/tools/build</tt>.
Assuming you're installing Boost.Build from released source distribution,
the following steps are needed. All paths are given relatively to
Boost.Build root directory, which is the directory with the document you
are reading.
<ol>
<li>Go to "jam_src" directory and build Boost.Jam. Two convenient
@@ -178,15 +177,21 @@
<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> -->
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>
<p>If you use Boost distribution, or Boost CVS, the Boost.Build root is
located at <tt>$boost_root/tools/build</tt> and the installation steps
are the same. However, don't skip the bjam rebuilding step, even if you
have a previous version. CVS version of Boost.Build requires CVS version
of Boost.Jam.</p>
<p>When starting a new project which uses Boost.Build, you need to make
sure that build system can be found. There are two ways.</p>
@@ -1016,17 +1021,17 @@ boost-build /path/to/boost.build ;
<li>It allows to have main target names with slashes.
<!-- The motivation for which is:
So, to summarize:
1. The project which extract tarfile may extract all possible kinds of
targets, and it's reasonable to use them directly from other project.
2. The rule for unpacking tar is inplemented in terms of "patch-file", for
maintainability, and therefore, must use main target name which contains
slashes?
3. Using sub-Jamfile in "foo" to declare extracted file "foo/b" is not an
option, because you should not change existing tree
So, to summarize:
1. The project which extract tarfile may extract all possible kinds of
targets, and it's reasonable to use them directly from other project.
2. The rule for unpacking tar is inplemented in terms of "patch-file", for
maintainability, and therefore, must use main target name which contains
slashes?
3. Using sub-Jamfile in "foo" to declare extracted file "foo/b" is not an
option, because you should not change existing tree
That makes good rationale for why main target must contain names.
-->
That makes good rationale for why main target must contain names.
-->
</li>
</ul>

55
v2/boost_build_v2.html
View File

@@ -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"
@@ -145,11 +145,10 @@
<hr>
<h2 id="installation">Installation</h2>
Assuming you're installing Boost.Build from sources, the following steps
are needed. All paths are given relatively to Boost.Build root directory,
which is the directory with the document you are reading. When using
Boost distribution, Boost.Build root is located at
<tt>$boost_root/tools/build</tt>.
Assuming you're installing Boost.Build from released source distribution,
the following steps are needed. All paths are given relatively to
Boost.Build root directory, which is the directory with the document you
are reading.
<ol>
<li>Go to "jam_src" directory and build Boost.Jam. Two convenient
@@ -178,15 +177,21 @@
<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> -->
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>
<p>If you use Boost distribution, or Boost CVS, the Boost.Build root is
located at <tt>$boost_root/tools/build</tt> and the installation steps
are the same. However, don't skip the bjam rebuilding step, even if you
have a previous version. CVS version of Boost.Build requires CVS version
of Boost.Jam.</p>
<p>When starting a new project which uses Boost.Build, you need to make
sure that build system can be found. There are two ways.</p>
@@ -1016,17 +1021,17 @@ boost-build /path/to/boost.build ;
<li>It allows to have main target names with slashes.
<!-- The motivation for which is:
So, to summarize:
1. The project which extract tarfile may extract all possible kinds of
targets, and it's reasonable to use them directly from other project.
2. The rule for unpacking tar is inplemented in terms of "patch-file", for
maintainability, and therefore, must use main target name which contains
slashes?
3. Using sub-Jamfile in "foo" to declare extracted file "foo/b" is not an
option, because you should not change existing tree
So, to summarize:
1. The project which extract tarfile may extract all possible kinds of
targets, and it's reasonable to use them directly from other project.
2. The rule for unpacking tar is inplemented in terms of "patch-file", for
maintainability, and therefore, must use main target name which contains
slashes?
3. Using sub-Jamfile in "foo" to declare extracted file "foo/b" is not an
option, because you should not change existing tree
That makes good rationale for why main target must contain names.
-->
That makes good rationale for why main target must contain names.
-->
</li>
</ul>