- Where should I download wxMac from?
- Which Mac platforms are supported?
-- How is the Mac OS X port different from the Classic Mac OS port?
-- How are improvements to the Classic Mac OS port integrated into the Mac OS X port?
- What compilers are supported?
+- What can I do if I get conflicts between different installed versions of wxWidgets?
- How does CVS handle file types/creators under Mac OS 8.x /9.x?
- How does CVS handle file types/creators under Mac OS X?
+
- What steps are required to build wxMac under Mac OS X?
- What important settings are required in the CodeWarrior Project Preferences?
- What are the smart preprocessing errors with the Apple Developer Tools?
@@ -45,45 +46,42 @@ 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.
-wxWidgets 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 wxWidgets 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 wxWidgets. 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.
+
+
@@ -106,6 +104,7 @@ All files checked out under Mac OS X will be untyped and CodeWarrior will not re