Update INSTALL to not mention the optional file formats and add info about building a framework

1 files changed, 22 insertions, 8 deletions

diff --git a/INSTALL b/INSTALL
index 2aba6b43..8391c0b3 100644
--- a/INSTALL
+++ b/INSTALL
@@ -9,21 +9,35 @@ This can be done using the following commands:
   make
   sudo make install
 
-Some file formats in TagLib are not enabled by default, you can compile
-support for MP4 and WMA using the following options:
-
-  cmake -DWITH_MP4=ON -DWITH_ASF=ON [...]
-
 In order to build the included examples, use the BUILD_EXAMPLES option:
 
   cmake -DBUILD_EXAMPLES=ON [...]
 
+See http://www.cmake.org/cmake/help/runningcmake.html for generic help on
+running CMake.
+
+Mac OS X Framework
+------------------
+
+On Mac OS X, you might want to build a framework that can be easily integrated
+into your application. If you set the BUILD_FRAMEWORK option on, it will compile
+TagLib as a framework. For example, the following command can be used to build
+an Universal Binary framework with Mac OS X 10.4 as the deployment target:
+
+  cmake -DCMAKE_BUILD_TYPE=Release \
+    -DBUILD_FRAMEWORK=ON \
+    -DCMAKE_C_COMPILER=/usr/bin/gcc-4.0 \
+    -DCMAKE_CXX_COMPILER=/usr/bin/c++-4.0 \
+    -DCMAKE_OSX_SYSROOT=/Developer/SDKs/MacOSX10.4u.sdk/ \
+    -DCMAKE_OSX_DEPLOYMENT_TARGET=10.4 \
+    -DCMAKE_OSX_ARCHITECTURES="ppc;i368;x86_64"
+
+Unit Tests
+----------
+
 If you want to run the test suite to make sure TagLib works properly on your
 system, you need to have cppunit installed. The test suite has a custom target
 in the build system, so you can run the tests using make:
 
   make check
 
-See http://www.cmake.org/cmake/help/runningcmake.html for generic help on
-running CMake.
-