Changes between Initial Version and Version 1 of CMakeBinaryInstaller

Timestamp:

Jun 14, 2007, 2:18:36 PM (15 years ago)

Author:

Douglas Gregor

Comment:

Initial description of packaging

CMakeBinaryInstaller

@@ +1 @@
+== Building a Binary Installer with CMake ==
+
+CMake can easily build binary installers 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, provided by the [http://www.cmake.org/Wiki/CMake:Packaging_With_CPack CPack] program that is part of CMake, is used to create all of CMake's binary installers. We use CPack to build binary installers for Boost. To build a binary installer for Boost, follow these steps:
+
+  1. [wiki:CMakeConfigAndBuild Configure and build] Boost using CMake. 
+  2. ('''Windows only''') Download and install the [http://nsis.sourceforge.net/Main_Page Nullsoft Scriptable Install System (NSIS)], which is used to create graphical installers on Windows. Unix users do not need to install any extra tools.
+  3. Using the same development tools for building Boost, build the "package" target to create the binary installers.
+    a. With Microsoft Visual Studio, build the target named {{{PACKAGE}}}. 
+    b. With makefiles, run
+    {{{
+make package
+    }}}
+
+The output of the packaging process will be one or more binary packages of the form Boost-''version''-''platform''.''extension''. The type of package will differ from one platform to another:
+  * On Windows: The primary output is an executable ({{{.exe}}}) package that provides a graphical installer.
+  * On Mac OS X: The primary output is a disk image ({{{.dmg}}}) that contains a graphical installer package.
+  * On Unix: Packaging produces compressed tarballs ({{{.tar.gz}}}) and a self-installing shell script ({{{.sh}}})