applied patch to build wxMSW with CW7 (patch 550445)
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@15472 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -354,17 +354,51 @@ compiling the sample again.
|
||||
Metrowerks CodeWarrior compilation
|
||||
----------------------------------
|
||||
|
||||
1. Downloaded and unzip wxWindows-x.y.z-cw.zip.
|
||||
2. Load the make_cw.mcp project in wx\src, and compile.
|
||||
3. Load the make_cw.mcp project in wx\samples\minimal, and compile.
|
||||
Further project files for samples will be available in due
|
||||
course.
|
||||
1. CodeWarrior Pro7 project files in XML format are already
|
||||
included in wxMSW-x.y.z.zip and the setup version.
|
||||
2. Review the file include\wx\msw\setup.h (or include\wx\msw\setup0.h if
|
||||
you are working from the CVS version) to make sure the settings reflect
|
||||
what you want. If you aren't sure, leave it alone and go with the
|
||||
default settings. A few notes:
|
||||
- Don't use wxUSE_DEBUG_NEW_ALWAYS: it doesn't mix well with MSL
|
||||
- wxUSE_GLOBAL_MEMORY_OPERATORS works, but memory leak reports
|
||||
will be rather confusing due to interactions with the MSL ANSI
|
||||
and runtime libs.
|
||||
3. The project file to build the Win32 wxWindows libraries relies on the
|
||||
Batch File Runner plug-in. This plug-in is not installed as part of
|
||||
a normal CW7 installation. However, you can find this plug-in on the
|
||||
CodeWarrior Reference CD, in the Thrill Seekers folder; it's call the
|
||||
"Batch File Post Linker".
|
||||
4. If you choose not to install the Batch File Runner plug-in, then you
|
||||
need to do the following by hand:
|
||||
(1) Create the directories lib\cw7msw\include\wx and copy the file
|
||||
include\wx\msw\setup.h (or include\wx\msw\setup0.h if you are
|
||||
working from the CVS version) to lib\cw7msw\include\wx\setup.h
|
||||
(2) Create the directories lib\cw7mswd\include\wx and copy the file
|
||||
include\wx\msw\setup.h (or include\wx\msw\setup0.h if you are
|
||||
working from the CVS version) to lib\cw7mswd\include\wx\setup.h
|
||||
5. Import srcwxWindows.xml to create the project file wxWindows.mcp.
|
||||
Store this project file in directory src. You may get warnings about
|
||||
not being able to find certain project paths; ignore these warnings, the
|
||||
appropriate paths will be created during the build by the Batch File Runner.
|
||||
6. Choose the wxlib Win32 debug or wxlib Win32 Release target and build. You
|
||||
will get some warnings about hidden virtual functions, illegal conversions
|
||||
from const pointers to pointers, etc., all of which you can safely ignore.
|
||||
***Note: if you get errors that the compiler can't find "wx/setup.h", just
|
||||
stop the build and build again. These errors occur because sometimes the
|
||||
compiler starts doing its thing before the copying of setup.h has completed.
|
||||
7. The following libraries will be produced depending on chosen
|
||||
target:
|
||||
- wx_x86.lib ANSI Release (static)
|
||||
- wx_x86_d.lib ANSI Debug (static)
|
||||
8. Sorry, I haven't had time yet to create and test unicode or DLL versions.
|
||||
Volunteers for this are welcome (as neither DLLs nor unicode builds are
|
||||
big priorities for me ;).
|
||||
9. CodeWarrior Pro7 project files (in XML format) are also provided for some
|
||||
of the samples. In particular, for the minimal, controls, dialogs, dnd,
|
||||
and docview samples. You can use these project files as templates for
|
||||
the other samples and for your own projects.
|
||||
|
||||
Note (1): you need CodeWarrior Pro 4 plus the patches to 4.1 from the
|
||||
Metrowerks Web site.
|
||||
|
||||
Note (2): unfortunately these files are not yet up-to-date for the
|
||||
current release.
|
||||
|
||||
Symantec C++ compilation
|
||||
------------------------
|
||||
|
Reference in New Issue
Block a user