X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/cd5082468fc4dd397d7eea951fa4e905ea3f9368..5acf8f1d43fb8544971f205989b8e01cd91d0ce3:/docs/html/faqmac.htm
diff --git a/docs/html/faqmac.htm b/docs/html/faqmac.htm
index 722f83ca55..eb10289a07 100644
--- a/docs/html/faqmac.htm
+++ b/docs/html/faqmac.htm
@@ -2,7 +2,7 @@
-wxWindows 2 for Mac FAQ
+wxWidgets for Mac FAQ
@@ -13,7 +13,7 @@
|
-wxWindows 2 for Mac FAQ
+wxWidgets for Mac FAQ
|
@@ -27,65 +27,65 @@ See also top-level FAQ page.
Please see the downloads page.
-The version of wxMac in CVS advances quickly so it is recommended that you download the
-the sources from the CVS trunk.
-There is also a wxMac 2.3.1 development snapshot.
The author of this port is Stefan Csomor.
-wxWindows 2 can be used to develop and deliver applications on Classic Mac OS (e.g. Mac OS 8.x/9.x) both as Carbon and non-Carbon applications.
-
-A Mac OS X port is in progress in order to be able to build wxWindows applications using the Apple Developer Tools that are delivered with every copy of Mac OS X.
-The Mac OS X port is based on and, for the most part, merged with the Carbon code for Classic Mac OS.
+wxWidgets can be used to develop and deliver applications on Mac OS X and Mac Classic (e.g. Mac OS 8.x/9.x) both as Carbon and non-Carbon applications.
+However the Mac OS X port is the most actively developed one, and Mac Classic will not be supported
+after 2.6. wxMac works best with Mac OS X 10.3 and above.
-
+
-wxMac for Mac OS X shares code both with wxMac for Mac OS and common Unix code in wxWindows. The aim is to use the same Mac OS Carbon code both for Classic Mac OS and for Mac OS X while leveraging the fact that Mac OS X is a BSD Unix.
+Under Classic Mac OS, MetroWerks CodeWarrior Pro 6 (or above) is required to build wxMac.
-This hybrid approach was suggested by Apple to the Fizzilla team working on Mozilla for Mac OS X.
+Under Mac OS X, the Developer Tools are sufficient to build wxMac. CodeWarrior Pro 6 can also be used to build the Carbon targets.
-
-
-Since the source code is shared between the two ports, any Carbon compliant improvements to wxMac for Classic Mac OS are automatically available in the Mac OS X port.
-
-The following points should be considered when improving wxMac:
-
-- Non Carbon compliant changes for Classic Mac OS will most likely break the Mac OS X port. Such changes should be tested using the Carbon targets in the CodeWarrior projects for Classic Mac OS.
-
- Non Carbon compliant changes for Mac OS X will most likely break the Classic Mac OS port. Such changes should be tested using CodeWarrior under Mac OS 8.x/9.x.
-
-
+
-
+Some versions of Mac OS X install an older version of wxMac than the one you may be using
+for development. This can cause conflicts, such as link errors when building your
+applications. A user reports:
-Under Classic Mac OS, MetroWerks CodeWarrior Pro 5.3 or 6 are required to build wxMac.
-
-Under Mac OS X, the Developer Tools are sufficient to build wxMac. CodeWarrior Pro 6 can also be used to build the Carbon targets.
-
+
+I got it to work. I removed the original wxMac build-release folder
+and recompiled wxMac following instructions in your book. I then ran
+"sudo make install" which I didn't do the first time. I figured I
+could now run wx-config --cxxflags from my home directory because
+/usr/local/bin/wx-config was in my $PATH. However, OSX 10.4 installed
+a version of wxWidgets. When I ran wx-config I was getting wx 2.5
+libs instead of the 2.6.1 libs I just compiled. When I ran
+"/usr/local/bin/wx-config --cxxflags" and "/usr/local/bin/wx-config --libs"
+and pasted that output into XCode preferences, everything worked fine.
+
+
-Before checking out the wxWindows code using a CVS client under Mac OS 8.x/9.x, be sure your computer is set up to treat xpm and xbm images correctly:
+Before checking out the wxWidgets code using a CVS client under Mac OS 8.x/9.x, be sure your computer is set up to treat xpm and xbm images correctly:
- bring up the Internet control panel, select the Advanced Options tab, click on the File Mapping icon from the list at the left and see if there are is an entry for ".xpm" files and another for ".xbm".
- if an entry exists, click Change... and make sure File Type is
TEXT (just those four capital letters); correct it if necessary. If there is no entry, make one with type set to TEXT and creator set to anything you like; reasonable choices include GKON (Graphic Converter) or CWIE (CodeWarrior).
@@ -99,11 +99,12 @@ The Mac OS X CVS client does not handle file types and creators at all (just lik
All files checked out under Mac OS X will be untyped and CodeWarrior will not recognize them correctly. To correct this, use the autotyper provided in the CVS sources:
-- decode and decompress the file
wxWindows/docs/mac/TypeAsMetrowerksText.sea.hqx
- - drag the wxWindows CVS sandbox directory onto the autotyper and most of the files will be typed according to the file extension
+
- decode and decompress the file
wxWidgets/docs/mac/TypeAsMetrowerksText.sea.hqx
+ - drag the wxWidgets CVS sandbox directory onto the autotyper and most of the files will be typed according to the file extension
+
@@ -137,8 +139,8 @@ You need to have the Apple Developer Tools installed. The Developer Tools CD is
Building wxMac completely without configure is not supported.
-Building wxWindows directly in the CVS sandbox is not recommended. Instead, wxWindows should be built in a directory configured relatively to the CVS sandbox.
-For instance, to build wxMac with configure, start in the base wxWindows directory and type:
+Building wxWidgets directly in the CVS sandbox is not recommended. Instead, wxWidgets should be built in a directory configured relatively to the CVS sandbox.
+For instance, to build wxMac with configure, start in the base wxWidgets directory and type:
mkdir macbuild
cd macbuild
@@ -195,15 +197,40 @@ This error can sometimes be corrected or avoided by modifying the source code. H
-Because wxWindows does not have a specific API for the About menu item or the Help menu, the Mac OS port uses some static variables to help the engine make the right decisions:
+Because wxWidgets does not have a specific API for the About menu item or the Help menu, the Mac OS port uses some static variables to help the engine make the right decisions:
- It assumes that the About menu item is part of a Help menu.
-
- The title of the Help menu is stored in
wxApp::s_macHelpMenuTitleName, it defaults to "&Help", but you can change it in your constructor to your specific menu title.
+ - The title of the Help menu is stored in
wxApp::s_macHelpMenuTitleName, it defaults to "&Help", but you can change it in your constructor to your specific menu title.
- The item Id of the About menu is stored in
wxApp::s_macAboutMenuItemID, it defaults to wxID_ABOUT, but can be changed as well to suit your needs.
- - The other items of the wxWindows help menu are appended to the Mac OS Help menu and the translation of Ids is handled transparently for your application.
+
- The other items of the wxWidgets help menu are appended to the Mac OS Help menu and the translation of Ids is handled transparently for your application.
+
+
+If you have Mac OS X, you have the icns editor somewhere in the
+Utilities folder. Create an icon using this tool and DeRez it, so that you have a .r
+file with a 'icns' resource with id (-16455). Include this .r file in
+your project and in the CodeWarrior Settings add a check mark under Linker:Output
+Flags/Finder Flags/Has Custom Icon.
+
+
+
+
+Sometimes you want to test your application against different versions
+of wxWidgets, for example a stable version of wxWidgets versus a development version.
+The easiest way to do this is to create a symbolic path.
+
+Under Edit-Preferences in General:Source Trees, type a name (for example WXWIN)
+and choose a path for it. Now reselect your include and lib paths for a last
+time, in the settings for each configuration, but make them relative to the symbolic name.
+
+
+From now on you can just change the path associated with the symbolic name.
+
+
+
+