X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/ef3f71c3d8eabf6b7ac31d662dca6e631c29a886..6ba5438dda164146bf36ca729f8328332fae36b7:/docs/mac/install.txt?ds=inline diff --git a/docs/mac/install.txt b/docs/mac/install.txt index ec1227d3ed..6fff2a4940 100644 --- a/docs/mac/install.txt +++ b/docs/mac/install.txt @@ -1,10 +1,10 @@ -wxWindows 2.5 for Mac installation ----------------------------------- +wxWidgets 2.6.2 for Mac installation +------------------------------------ On MacOS X, you can download Apple's free developer tools (gcc and associated headers and libraries, such as the Carbon API). You can then use configure in a similar way to compiling -wxWindows on Linux (or on Windows using MinGW or Cygwin). See +wxWidgets on Linux (or on Windows using MinGW or Cygwin). See 'Apple Developer Tools' below for more details on using configure. @@ -17,37 +17,11 @@ each type of application on the target operating system. Installing latest headers (and Carbon Support) ---------------------------------------------- -NOTE: these steps are not necessary for CW Pro 6 and above, -only for CW Pro 5.3. - -The latest build for carbon support leads to a few changes you will have to -follow, in order to successfully compile the code (also necessary if you don't -want to build the carbon targets). - -1. You need CodeWarrior Pro 5.3 , i.e. 5.0 with all the upgrades. -2. You have to download the 3.4.0 (or greater) universal interfaces from - ftp://ftp.apple.com/developer/Development_Kits/UniversalHeaders3.4.1.img.bin. -3. put the Interfaces and Libraries Folder into the MacOS Support folder and - replace older versions. -4. remove from the MacOS Support folder the separate OpenTransport folder. -5. open the file MacOS Support:MacHeaders:MacHeaders.c and add the line - #include - after the - #include -6. rebuild all MacHeaders from the MacHeaders.mcp project in the same folder. - -If you want to build the carbon targets, you will also need the latest -carbonized version of MSL from Metrowerks, at the time of writing, this meant -applying the changes from the folders: - -CodeWarrior Pro 5:Pre-Release:Carbon & MacOSX Development:Carbonized MSL and -CodeWarrior Pro 5:Pre-Release:Carbon & MacOSX Development:Carbonized Runtimes -(consult the file CodeWarrior Pro 5:Pre-Release:Carbon & MacOSX Development:Carbon & MacOSX README) - Patching headers: CodeWarrior 8.x --------------------------------- -If you run into trouble with WCHAR_MIN and WCHAR_MAX in ansi.h, +If you run into trouble with WCHAR_MIN and WCHAR_MAX the for +MacOS X Support:Headers:(wchar_t Support fix):machine:ansi.h, apply the patch ansi.diff. You may also need to comment out the _T definition in @@ -83,32 +57,14 @@ Project Files The project files are stored as xml text files and converted to binary CodeWarrior projects in the distribution (see AppleScript Files below): - - *M5.xml -> *M5.mcp for CodeWarrior 5.3 - - *M6.xml -> *M6.mcp for CodeWarrior 6 - - *M7.xml -> *M7.mcp for CodeWarrior 7 and above. - -In order to build the library (and then the samples) you need to make the -following projects (for CW 5.3, similar process for CW 7): - -:src:wxwindowsM5.mcp -:src:png:pngM5.mcp -:src:tiff:tiffM5.mcp -:src:jpeg:jpegM5.mcp -:src:zlib:zlibM5.mcp -Note that if using CW 8 and above, when compiling the samples -you may need to edit the target settings, click on Language -Settings, C/++ Language and remove the forward slash at the -start of /wx/wx_cw_d.h (or similar filename). + - *M8.xml -> *M8.mcp for CodeWarrior 8 and above. AppleScript Files ----------------- Several AppleScript files are provided in the docs:mac directory: - - M5xml2mcp.applescript to convert xml files to CodeWarrior 5 projects - - M5mcp2xml.applescript to convert CodeWarrior 5 projects to xml files - - M5build.applescript to automatically build all samples/demos projects - M8xml2mcp.applescript to convert xml files to CodeWarrior 8 projects - M8mcp2xml.applescript to convert CodeWarrior 8 projects to xml files - SetXMLCreator.applescript to set correct creator type (see below) @@ -145,10 +101,10 @@ account marked as a "Computer Administrator". Then 7) type Note that while using this method is okay for development, it is not -recommended that you require endusers to install wxWindows into their +recommended that you require endusers to install wxWidgets into their system directories in order to use your program. One way to avoid this -is to configure wxWindows with --disable-shared. Another way to avoid -it is to make a framework for wxWindows. Making frameworks is beyond +is to configure wxWidgets with --disable-shared. Another way to avoid +it is to make a framework for wxWidgets. Making frameworks is beyond the scope of this document. Note: