download.html 7.2 KB

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