Changes between Version 2 and Version 3 of CMakeConfigAndBuild

Timestamp:

Jun 12, 2007, 6:11:45 AM (15 years ago)

Author:

Douglas Gregor

Comment:

Finish configure & build instructions

CMakeConfigAndBuild

@@ -28 +28 @@
             }}}
             i. Press `c` (for (c)onfigure) to perform the preliminary configuration of the CMake build system.
-            i. If you want, you can edit various options in the CMake interface. These options will affect what libraries are built and how. Each time you finish editing options, press `c` to reconfigure.
+            i. If you want, you can edit various options in the CMake interface. These options will affect what libraries are built and how. Each time you finish editing options, press `c` to reconfigure. '''Mac OS X users''': to build universal binaries, change the value of `CMAKE_OSX_ARCHITECTURES` to `ppc;i386` in the CMake configuration.
             i. When the options you have selected have stabilized, CMake will give you the (g)enerate option. If you do not see this option, press `c` again to reconfigure. Finally, press `g` to generate makefiles and exit.
 
     That's it! You've now configured your source tree and are ready to start building Boost.
 
-  4. Build Boost: Like configuration, the way in which one builds Boost with CMake differs from one platform to another, depending on
+  4. Build Boost: 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.
+       a. '''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.
+       a. '''On Unix''' (and when using makefile variants on Microsoft Windows): If you are on Unix, you will build Boost using standard "make" tools. Change into the binary directory we created and configured earlier, than run `make`:
+       {{{
+make
+       }}}
+
+  5. 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. 
+
+== 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.,
+{{{
+make install
+}}}
+
+== Packaging Boost ==
+CMake can easily build binary packages for a variety of platforms. On Windows and Mac OS X, CMake builds graphical installation programs. For other Unix operating systems, CMake currently builds tarballs and self-installing shell scripts. This CMake functionality, providing by the CPack program that is part of CMake, is used to create all of the CMake's binary installers.
+
+Building binary installation packages with CMake is similar to installing Boost. On Windows, one must first download and install the [http://nsis.sourceforge.net/Main_Page Nullsoft Scriptable Install System (NSIS)]. Then, using Microsoft Visual Studio, one loads the Boost project/solution and build the `PACKAGE` target to generate the graphical installer. On Mac OS X, other Unix platforms, and on Windows when using a makefile generator, change into the Boost binary directory and use the `package` make target, e.g.,
+{{{
+make package
+}}}
+
+Once this process completes, you will have several binary installers for you platform.