X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/8b283bb88e49a83785c7fbe94fdb0203052022ce..61c213fe224da24ce33c9187263e75a17ca83a04:/docs/html/faqmac.htm diff --git a/docs/html/faqmac.htm b/docs/html/faqmac.htm index 1357289d66..6c053adb95 100644 --- a/docs/html/faqmac.htm +++ b/docs/html/faqmac.htm @@ -1,18 +1,19 @@ +
-- -wxWindows 2 for Mac FAQ + | + +wxWidgets 2 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. +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.
This hybrid approach was suggested by Apple to the Fizzilla team working on Mozilla for Mac OS X.
@@ -93,7 +87,7 @@ Under Mac OS X, the Developer Tools are sufficient to build wxMac. CodeWarrior P
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,8 +101,8 @@ 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
+@@ -131,11 +125,11 @@ This is also necessary even if you don'want to build the Carbon targets.
Build the projects (makemac6.mcp
for CodeWarrior Pro 6; makemac.mpc
for CodeWarrior Pro 5) in the following five directories:
@@ -145,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
@@ -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. + +
+ +