download.html 6.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  2. <html>
  3. <head>
  4. <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  5. <title>Boost Download and Installation</title>
  6. </head>
  7. <body bgcolor="#FFFFFF" text="#000000">
  8. <table border="1" bgcolor="#007F7F" cellpadding="2">
  9. <tr>
  10. <td bgcolor="#FFFFFF"><img src="../c++boost.gif" alt="c++boost.gif (8819 bytes)" width="277" height="86"></td>
  11. <td><a href="../index.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>Home</big></font></a></td>
  12. <td><a href="../libs/libraries.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>Libraries</big></font></a></td>
  13. <td><a href="../people/people.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>People</big></font></a></td>
  14. <td><a href="faq.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>FAQ</big></font></a></td>
  15. <td><a href="index.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>More</big></font></a></td>
  16. </tr>
  17. </table>
  18. <h1>Boost Download and Installation</h1>
  19. The boost libraries are intended for easy download and <a href="#Installation">installation</a>;
  20. many libraries require nothing more that downloading and unpacking to be ready
  21. for use, including full documentation.&nbsp; When required, see <a href="../tools/build/index.html">Building
  22. Boost Libraries</a> to create object libraries.
  23. <h2>Download</h2>
  24. The boost libraries are available in various formats:
  25. <ul>
  26. <li><a href="http://boost.sourceforge.net/release/">HTTP download</a> all of Boost as a single archive
  27. file (<a href="#.zip">.zip</a> or <a href="#.tar.gz">.tar.gz</a>) file from our
  28. SourceForge HTTP site. Older versions also available. (This option is
  29. suggested first since it doesn't count against our web site host's monthly
  30. fee.)</li>
  31. </ul>
  32. <ul>
  33. <li><a href="../boost_all.zip">ZIP download</a> all of Boost as a single archive
  34. file from our web site.</li>
  35. </ul>
  36. <ul>
  37. <li><a href="../boost_all.tar.gz">TAR.GZ download</a> all of Boost as a single archive
  38. file from our web site.</li>
  39. </ul>
  40. <ul>
  41. <li><a href="#CVS">Command line, GUI</a>, or <a href="#Browser">browser</a> access
  42. to Boost's <a href="http://sourceforge.net/cvs/?group_id=7586">CVS repository</a>.</li>
  43. </ul>
  44. <ul>
  45. <li>Download individual files from links in the documentation on the web
  46. site.&nbsp; Because of the number of files involved, and <a href="../libs/hdr_depend.html">header
  47. dependencies</a>, this option usually isn't very useful.</li>
  48. </ul>
  49. <h3><a name=".zip">.zip</a> file</h3>
  50. The .zip format is widely supported by both free decoders and
  51. commercial compress/archive utilities. If you don't already have a
  52. .zip file decoder, download one from the
  53. <a href="http://www.info-zip.org/">Info-ZIP</a>
  54. web site, which supplies versions for many operating systems.
  55. <p>
  56. Text file line endings in the .zip file are as supplied by each library
  57. developer.&nbsp; This works fine for Windows, but not for Unix/Linux.&nbsp; The
  58. .tar.gz file supplies Unix/Linux friendly line endings.
  59. <h3><a name=".tar.gz">.tar.gz</a> file</h3>
  60. The .tar.gz format is widely supported on Unix/Linux platforms. Some
  61. Windows compress/archive utilities can read the format as well.&nbsp; Because
  62. the gzip format compresses the archive as a single file rather than compressing
  63. each file individually, the .tar.gz file is smaller that the .zip file.
  64. <p>Text file line endings in the .tar.gz file have been converted to newlines
  65. for ease of use on Unix/Linux platforms.</p>
  66. <h3>Boost CVS access via command line or graphical clients</h3>
  67. For those who have CVS clients installed, the libraries are also available from
  68. the public <a href="http://sourceforge.net/cvs/?group_id=7586">Boost CVS
  69. repository</a>. Free command line clients (often already installed on Linux/Unix
  70. systems) are available at the <a href="http://www.cvshome.org/">CVS home page</a>,
  71. and free GUI clients are also available for Windows, Mac, and other systems from
  72. <a href="http://www.cvsgui.org/">CvsGui.org</a>.<p>The general procedure for
  73. command-line clients is something like this: </p>
  74. <blockquote>
  75. <code>
  76. cvs -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost login
  77. </code>
  78. <br>
  79. [Hit &lt;return&gt; when it asks for a password]
  80. <br>
  81. <code>
  82. cvs -z3 -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost checkout boost
  83. <br>
  84. cvs -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost logout
  85. </code>
  86. </blockquote>
  87. Read the manual for your CVS client for further information.
  88. <p>
  89. This access is read-only; if you are a library author and wish to have
  90. CVS write access, please contact one of the
  91. <a href="mailto:boost-owner@yahoogroups.com">moderators</a>.
  92. <h3>Boost CVS access via web <a name="Browser">Browser</a></h3>
  93. For access to the CVS archive from any modern web browser, you can
  94. also use the <a
  95. href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost/boost/">web
  96. browser&nbsp; interface</a>.&nbsp; Try one of the color diffs to see
  97. how a file has changed over time.
  98. <h2><a name="Installation">Installation</a></h2>
  99. Boost does not yet have a standardized installation process. There has
  100. been some interest in developing one; as of this writing <a
  101. href="../people/william_kempf.htm">Bill Kempf</a> has volunteered to
  102. coordinate and is gathering volunteers. If you have expertise in this
  103. area (particularly cross-platform expertise), and you would like to
  104. contribute, please announce your availability on the
  105. <a
  106. href="http://lists.boost.org/mailman/listinfo.cgi/boost-install">Boost
  107. Install</a> mailing list.
  108. <p>
  109. That said, preparing to use Boost in a development project is
  110. relatively straightforward. Most boost libraries are implemented
  111. entirely within their header files. The only preparation for their
  112. use is to add the boost root directory to your compiler's list of
  113. <code>#include&lt;...&gt;</code> search paths. For example,
  114. using Windows 2000, if you have unzipped release 1.28.0 from
  115. boost_all.zip into the top level directory of your C drive, adding
  116. '-Ic:/boost_1_28_0' to the command line of most compilers is
  117. sufficient.
  118. <p>
  119. The <a href="../libs/python/doc/index.html">Python</a>, <a
  120. href="../libs/regex/index.htm">Regex</a>, and <a
  121. href="../libs/thread/doc/index.html">Threads</a> libraries are
  122. implemented in part as separate source files, and thus require
  123. compilation before use. See <a
  124. href="../tools/build/index.html">Building Boost Libraries</a> for an
  125. automatic tool to prepare such libraries. Some of the individual
  126. libraries also include make and/or project files for various
  127. compilers, but every library also
  128. <p>
  129. <hr>
  130. Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->16 May, 2002<!--webbot bot="Timestamp" endspan i-checksum="13975" -->
  131. <p>Written by&nbsp; <a href="../people/jens_maurer.htm">Jens Maurer</a>
  132. 2001-02-11</p>
  133. </body>
  134. </html>
粤ICP备19079148号