Changes between Version 11 and Version 12 of CMakeConfigAndBuild

Timestamp:

Aug 14, 2007, 5:36:42 PM (15 years ago)

Author:

Douglas Gregor

Comment:

Binary -> Build

CMakeConfigAndBuild

@@ -37 +37 @@
 mkdir $BOOST/build 
 }}}
-Change into the binary directory you have just created:
+Change into the build directory you have just created:
 {{{
 cd $BOOST/build 
@@ -83 +83 @@
 Like configuration, the way in which one builds Boost with CMake differs from one platform to another, depending on your platform and how you configured CMake. Either way, you'll be using the tools provided to you by your compiler or operating system vendor.
 === Microsoft Visual Studio === 
-If you have generated project files for Microsoft Visual Studio, you will need to start up Visual Studio to build Boost. Once Visual Studio has loaded, load the solution or project`Boost` from the Boost binary directory you set in the CMake configuration earlier. Then, just click "Build" to build all of Boost.
+If you have generated project files for Microsoft Visual Studio, you will need to start up Visual Studio to build Boost. Once Visual Studio has loaded, load the solution or project`Boost` from the Boost build directory you set in the CMake configuration earlier. Then, just click "Build" to build all of Boost.
 === On Unix (and when using makefile variants on Microsoft Windows) === 
 One builds using standard "make" tools. In the directory $BOOST/build (where the generated makefiles are) run `make`:
@@ -90 +90 @@
 }}}
 
-That's it! Once the build completes (which make take a while, if you are building all of the Boost libraries), the Boost libraries will be available in the `lib` subdirectory of your binary directory, ready to be used, installed, or packaged. 
+That's it! Once the build completes (which make take a while, if you are building all of the Boost libraries), the Boost libraries will be available in the `lib` subdirectory of your build directory, ready to be used, installed, or packaged. 
 
 == Installing Boost ==
-The installation of Boost's headers and compiled libraries uses the same tools as building the library. With Microsoft Visual Studio, just load the Boost solution or project and build the 'INSTALL' target to perform the installation. Unix and makefile users will change into the Boost binary directory and use the `install` make target, e.g.,
+The installation of Boost's headers and compiled libraries uses the same tools as building the library. With Microsoft Visual Studio, just load the Boost solution or project and build the 'INSTALL' target to perform the installation. Unix and makefile users will change into the Boost build directory and use the `install` make target, e.g.,
 {{{
 make install