| - -wxWindows 2 for Mac FAQ + | + +wxWidgets for Mac FAQ |
| - - -Please note that the version of wxMac in CVS is more robust and nearly feature-complete compared with the packaged 2.0 release. -Until a new release is made, it is recommended that you download the wxMac 2.3.1 development snapshot or the sources from the CVS trunk. - - | -
+The author of this port is Stefan Csomor.
-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.
-
-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.
-
-The following points should be considered when improving wxMac: -
+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 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. ++
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:
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).
@@ -107,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:
wxWindows/docs/mac/TypeAsMetrowerksText.sea.hqx
-wxWidgets/docs/mac/TypeAsMetrowerksText.sea.hqx
++
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
@@ -203,15 +197,40 @@ This error can sometimes be corrected or avoided by modifying the source code. H
wxApp::s_macHelpMenuTitleName, it defaults to "&Help", but you can change it in your constructor to your specific menu title.
+wxApp::s_macHelpMenuTitleName, it defaults to "&Help", but you can change it in your constructor to your specific menu title.
wxApp::s_macAboutMenuItemID, it defaults to wxID_ABOUT, but can be changed as well to suit your needs.
-+
+ +
+ +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. + +
+ +