download.html 5.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140
  1. <html>
  2. <head>
  3. <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  4. <title>Boost Download and Installation</title>
  5. </head>
  6. <body bgcolor="#FFFFFF" text="#000000">
  7. <table border="1" bgcolor="#007F7F" cellpadding="2">
  8. <tr>
  9. <td bgcolor="#FFFFFF"><img src="../c++boost.gif" alt="c++boost.gif (8819 bytes)" width="277" height="86"></td>
  10. <td><a href="../index.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>Home</big></font></a></td>
  11. <td><a href="../libs/libraries.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>Libraries</big></font></a></td>
  12. <td><a href="../people/people.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>People</big></font></a></td>
  13. <td><a href="faq.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>FAQ</big></font></a></td>
  14. <td><a href="index.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>More</big></font></a></td>
  15. </tr>
  16. </table>
  17. <h1>Boost Download and Installation</h1>
  18. The boost libraries are intended for easy download and <a href="#Installation">installation</a>;
  19. many libraries require nothing more that downloading and unpacking to be ready
  20. for use, including full documentation.&nbsp; When required, see <a href="../tools/build/index.html">Building
  21. Boost Libraries</a> to create object libraries.
  22. <h2>Download</h2>
  23. The boost libraries are available in various formats:
  24. <ul>
  25. <li><a href="http://boost.sourceforge.net/release/">HTTP download</a> all of Boost as a single archive
  26. file (<a href="#.zip">.zip</a> or <a href="#.tar.gz">.tar.gz</a>) file from our
  27. SourceForge HTTP site. Older versions also available. (This option is
  28. suggested first since it doesn't count against our web site host's monthly
  29. fee.)</li>
  30. </ul>
  31. <ul>
  32. <li><a href="../boost_all.zip">ZIP download</a> all of Boost as a single archive
  33. file from our web site.</li>
  34. </ul>
  35. <ul>
  36. <li><a href="../boost_all.tar.gz">TAR.GZ download</a> all of Boost as a single archive
  37. file from our web site.</li>
  38. </ul>
  39. <ul>
  40. <li><a href="#CVS">Command line</a> or <a href="#Browser">browser</a> access
  41. to Boost's CVS repository.</li>
  42. </ul>
  43. <ul>
  44. <li>Download individual files from links in the documentation on the web
  45. site.&nbsp; Because of the number of files involved, and <a href="../libs/hdr_depend.html">header
  46. dependencies</a>, this option usually isn't very useful.</li>
  47. </ul>
  48. <h3><a name=".zip">.zip</a> file</h3>
  49. The .zip format is widely supported by both free decoders and
  50. commercial compress/archive utilities. If you don't already have a
  51. .zip file decoder, download one from the
  52. <a href="http://www.info-zip.org/">Info-ZIP</a>
  53. web site, which supplies versions for many operating systems.
  54. <p>
  55. Text file line endings in the .zip file are as supplied by each library
  56. developer.&nbsp; This works fine for Windows, but not for Unix/Linux.&nbsp; The
  57. .tar.gz file supplies Unix/Linux friendly line endings.
  58. <h3><a name=".tar.gz">.tar.gz</a> file</h3>
  59. The .tar.gz format is widely supported on Unix/Linux platforms. Some
  60. Windows compress/archive utilities can read the format as well.&nbsp; Because
  61. the gzip format compresses the archive as a single file rather than compressing
  62. each file individually, the .tar.gz file is smaller that the .zip file.
  63. <p>Text file line endings in the .tar.gz file have been converted to newlines
  64. for ease of use on Unix/Linux platforms.</p>
  65. <h3><a name="CVS">CVS</a> command line access</h3>
  66. For those who have CVS installed, the libraries are also available
  67. from the public CVS repository. The general procedure for
  68. command-line clients is something like this:
  69. <blockquote>
  70. <code>
  71. cvs -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost login
  72. </code>
  73. <br>
  74. [Hit &lt;return&gt; when it asks for a password]
  75. <br>
  76. <code>
  77. cvs -z3 -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost checkout boost
  78. <br>
  79. cvs -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost logout
  80. </code>
  81. </blockquote>
  82. Read the manual for your CVS client for further information.
  83. <p>
  84. This access is read-only; if you are a library author and wish to have
  85. CVS write access, please contact one of the
  86. <a href="mailto:boost-owner@yahoogroups.com">moderators</a>.
  87. <h3>CVS <a name="Browser">Browser</a> access via WebCVS</h3>
  88. For access to the CVS archive from any modern web browser, you can also use the <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost/boost/">web
  89. browser&nbsp; interface</a>.&nbsp; Try one of the color diffs to see how a file
  90. has changed over time.
  91. <h2><a name="Installation">Installation</a></h2>
  92. Many boost libraries are implemented entirely within their header
  93. files. The only preparation for their use is to add the path for the
  94. parent directory of the boost headers sub-directory to your compiler's
  95. list of <code>#include</code> search directories.
  96. <p>
  97. For example, using Windows 2000, if you have unzipped release 1.20.2
  98. from boost_all.zip into the top level directory of your C drive, for
  99. Borland, GCC, and Metrowerks compilers add '-Ic:/boost_1_20_2' to the
  100. compiler command line, and for the Microsoft compiler add '/I
  101. "c:/boost_1_20_2"'. For IDE's, add 'c:/boost_1_20_2' (or whatever you
  102. have renamed it to) to the search list using the appropriate GUI
  103. dialog.
  104. <p>
  105. Some Boost libraries are implemented as separate source files, and
  106. thus require compilation into object libraries before any use. See <a href="../tools/build/index.html">Building
  107. Boost Libraries</a> for an automatic tool to prepare such libraries.
  108. Some of the individual libraries also include make and/or project files
  109. for various compilers, but these will become obsolete as Boost.Build matures..
  110. <p>
  111. <hr>
  112. Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->24 September, 2001<!--webbot bot="Timestamp" endspan i-checksum="39337" -->
  113. <p>Written by&nbsp; <a href="../people/jens_maurer.htm">Jens Maurer</a>
  114. 2001-02-11</p>
  115. </body>
  116. </html>
粤ICP备19079148号