Changes between Version 6 and Version 7 of CMakeConfigAndBuild


Ignore:
Timestamp:
Jun 12, 2007, 7:31:38 PM (15 years ago)
Author:
troy d. straszheim
Comment:

prettification of packaging section

Legend:

Unmodified
Added
Removed
Modified
  • CMakeConfigAndBuild

    v6 v7  
    9999
    100100== Packaging Boost ==
     101
    101102CMake 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.
    102103
    103 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.,
     104Building binary installation packages with CMake is similar to installing Boost.
     105=== On Windows ===
     106One 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.
     107=== On Mac OS X, other Unix platforms, and on Windows when using a makefile generator ===
     108change into $BOOST/build and use the `package` make target, e.g.,
    104109{{{
    105110make package