-Installing wxWidgets 2.6.2
+Installing wxWidgets 2.7.0
-----------------------------------------------------------
-This is wxWidgets 2.6.2 for Microsoft Windows 9x/ME, Windows NT,
+This is wxWidgets 2.7.0 for Microsoft Windows 9x/ME, Windows NT,
Windows 2000, Windows XP and Windows CE.
These installation notes can be found in docs/msw/install.txt
Please note that the VC++ 6.0 project files will work for VC++ .NET also.
-Also note that you can make the project files work with VC++ 5.0 but you'll
-need to edit .dsp file by hand before this is possible (change the version in
-the .dsp file header from 6.0 to 5.0).
+VC++ 5.0 can also be used, providing Service Pack 3 is applied. Without it
+you will have trouble with internal compiler errors. It is available for
+download at: ftp://ftp.microsoft.com/developr/visualstudio/sp3/full.
Using project files (VC++ 6 and later):
know you won't need some of the libraries (i.e. html part), you don't have
to compile it. It will also produce similar variations on jpeg.lib,
png.lib, tiff.lib, zlib.lib, and regex.lib.
+
If you want to build DLLs, you have to either build them one by one in
proper order (jpeg, png, tiff, zlib, regex, expat, base, core, the rest
in any order) or to use wx_dll.dsw workspace which has correct dependencies.
+ Unfortunately, VC++ 6 (but not VC++ 7 and later) doesn't always respect the
+ dependencies among the projects so you may still get linking errors due to
+ wrong build order. If this happens, please just start the build again and
+ eventually all the libraries will be built.
3. Open a sample project file, choose a configuration such as
Win32 Debug using Build | Set Active Configuration..., and compile.
The project files don't use precompiled headers, to save disk
corresponding 32-bit target for some files. Therefore after building
for one CPU it is necessary to clean the build before building the
equivalent target for another CPU. We've reported the problem to MS
- so maybe this will be fixed before VS 2005 ships.
+ but they say it is not possible to fix it.
3. To build, go to the 'Build' menu and choose 'Batch Build...'. Tick all the
all the 'x64|Debug' or all the 'Itanium|Debug' projects, and click 'Build'.
Using makefiles:
1. Open a 64-bit build command prompt, for either x64 or Itanium. Change
- directory to build\msw. Then for x64 type (note upper case):
+ directory to build\msw. Then for x64 type:
nmake -f makefile.vc TARGET_CPU=AMD64
See http://support.microsoft.com/?id=894573 for more information.
-Borland C++ 5.0/5.5 compilation
+Borland C++ compilation
----------------------------------------------------------------
-Compiling using the makefiles (updated 24 Sept 02):
+The minimum version required is 5.5 (last version supported by BC++ 5.0 was
+2.4.2), which can be downloaded for free from:
+http://www.borland.com/products/downloads/download_cbuilder.html#
+
+Compiling using the makefiles:
1. Change directory to build\msw. Type 'make -f makefile.bcc' to
make the wxWidgets core library. Ignore the compiler warnings.
Note (3): If you wish debug messages to be sent to the console in
debug mode, edit makefile.bcc and change /aa to /Tpe in link commands.
-Compiling using the IDE files for Borland C++ 5.0: not supported - please
-use version 2.4.1 (using the make utility in commandline mode works fine_
+Cmpilation succeeds with CBuilderX personal edition and CBuilder6, but
+you may have to copy make.exe from the 5.5 download to the new bin directory.
+Compiling using the IDE files for Borland C++ 5.0 and using CBuilder IDE
+(v1-v6): not supported
-Compiling using CBuilder (v1-v6): not supported - please
-use version 2.4.1 (using the make utility in commandline mode works fine_
** REMEMBER **
Metrowerks CodeWarrior compilation
----------------------------------------------------------------
+** NOTE: We don't use Metrowerks compiler any more and so depend on
+** your contributions to keep it up to date. It is possible that
+** the project files mentioned below are out of date due to recently
+** added files, please add them manually if you get linking errors.
+** The authoritative list of files is in build/bakefiles/files.bkl
+
1. CodeWarrior Pro 7 project files in XML format are already
- included in wxMSW-2.6.2.zip and the setup version.
+ included in wxMSW-2.7.0.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
----------------------------------------------------------------
NOTE: The makefile.gcc makefiles are for compilation under MinGW using
- native make and Windows command interpreter (command.com/cmd.exe), they
- won't work in other environments (such as UNIX or Unix-like, e.g. MSYS;
- you have to use configure instead)
+ Windows command interpreter (command.com/cmd.exe), they won't work in
+ other environments (such as UNIX or Unix-like, e.g. MSYS where you have
+ to use configure instead, see the section below)
Here are the steps required using the provided makefiles:
cd build-debug
../configure --with-msw --enable-debug --enable-debug_gdb --disable-shared
make
- make install % This step is optional, see note (8) below.
+ make install % This step is optional, see note (6) below.
cd samples/minimal
make
./minimal.exe
projects / wxWidgets.git / blobdiff