wxWidgets 2 for Mac FAQ

X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/2a3476f24d0d0d2d644bb3d06c616b740f3e1f29..8ffbb0f8df8e4c2facffc65c394c8933ac79c3af:/docs/html/faqmac.htm diff --git a/docs/html/faqmac.htm b/docs/html/faqmac.htm index 3e7f255569..eb10289a07 100644 --- a/docs/html/faqmac.htm +++ b/docs/html/faqmac.htm @@ -2,7 +2,7 @@ -wxWidgets 2 for Mac FAQ +wxWidgets for Mac FAQ @@ -13,7 +13,7 @@ -wxWidgets 2 for Mac FAQ +wxWidgets for Mac FAQ @@ -27,12 +27,13 @@ See also top-level FAQ page.

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 using CodeWarrior P ro 5.3?
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?

top-level FAQ page

Where should I download wxMac from?

downloads page

CVS trunk

development snapshot

The author of this port is Stefan Csomor.

Which Mac platforms are supported?

-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.

How is the Mac OS X port different from the Classic Mac OS port?

What compilers are supported?

-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.

How are improvements to the Classic Mac OS port integrated into 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. -

What can I do if I get conflicts between different installed versions of wxWidgets?

What compilers are supported?

-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. +

How does CVS handle file types/creators under Mac OS 8.x/9.x?

What steps are required to build wxMac under Mac OS X?

@@ -200,7 +200,7 @@ This error can sometimes be corrected or avoided by modifying the source code. H 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 wxWidgets help menu are appended to the Mac OS Help menu and the translation of Ids is handled transparently for your application.