***********************************************************************
*** Mac OS X Platform-Specific README FILE ***

If you have not already done so, please read the all-platform introductory file, /README_FIRST.TXT, which is located in the same directory as this file.


***********************************************************************
*** System Requirements / Installation ***

* This code distribution supports Mac OS X 10.2 and 10.3

* The contents of the book's CDROM must be copied (keeping the hierarchy) to the local machine, as described in README_FIRST.TXT

* The Mac OS X Developer Tools must be installed.  These can usually be found on a separate
disk, as part of your OS suite.

***********************************************************************
*** MacOS Specifics ***

The system must have the Mac OS X Developer Tools installed. 

This CDROM was built and tested using Mac OS 10.2.8.

***********************************************************************
*** Building Libraries and Demo Applications ***

The libraries and applications use the OpenGL GLUT system.  GLUT should be included as part of the Developer Tools installation.  As a result, there should be no need to add any path to GLUT into your development tool settings.

The MacOS platform uses "make" from a command prompt to build any or all of the libraries and demo applications.  A hierarchical build system allows the user to rebuild at any desired level in the code hierarchy.

To build, open a Terminal shell and change directory to the desired directory:

* To build or rebuild all Iv libraries in a single command, change directories to /common and build as described below.

* To build or rebuild a specific Iv library (such as IvMath), change directories to the /common subdirectory for the library (e.g. /common/IvMath) and build as described below.

* The library makefiles copy that library's header files to /common/Includes at the end of compilation.  In addition, the library itself is built to the /common/Libs subdirectory that matches the build configuration (OSXRelease or OSXDebug).  However, the libraries themselves reference other Iv library headers directly from that library's source directory.  As a result, the libraries may be built in any order.

* To rebuild all demo applications for all chapters in a single command, change directories to /Examples and build as described below.

* To rebuild all demo applications for a specific chapter in a single command (such as Chapter 3), change directories to that chapter's subdirectory under /Examples (e.g. /Examples/Ch03-Xforms) and build as described below.

* To rebuild a specific demo application, change directories to that demo's subdirectory under /Examples/Ch* and build as described below.

* To build, note that MacOS IS NOT THE DEFAULT PLATFORM.  To build any part of the code for MacOS, use the following commands in the desired build directory:

* For release builds:

make PLATFORM=OSX

OR

make release PLATFORM=OSX

* For debugging builds:

make debug PLATFORM=OSX

* To clear out all builds of the current directory for MacOS

make clean PLATFORM=OSX


***********************************************************************
*** Running Demo Applications ***

* The demos may be run from the command line (no application bundles, sorry).  The demo executables are built into the same directory as the demo's source files.  The release executable is Example, and the debug executable is ExampleD.

* Some of the demos have no data files and may thus be run from any location.  However, numerous demos use local data files in the current directory.  As a result, it is best to run the demos from the directory to which they were built.

***********************************************************************




