Microsoft Visual C++ compilation
--------------------------------
+You may wish to visit http://wiki.wxwindows.org/wiki.pl?MSVC for a more
+informal and more detailed description of the process summarized below.
+
Please note that the VC++ 6.0 project files will work for VC++ .NET also, but
you must open the .dsp files and not the .dsw files and in this case you will
need to manually build the other .dsp on which wxWindows.dsp depends: jpeg,
You may like to use the short form as shown by a dos directory listing ;
eg instead of c:\wxwindows-2.5.0 use c:\wxwind~1.4
Reboot if needed for the changes to autoexec.bat to take effect.
+
2. Change directory to src\msw. Type 'make -f makefile.b32' to
make the wxWindows core library. Ignore the compiler warnings.
This produces a library in the wxwindows\lib directory called
wx32ds.lib
+
3. Change directory to a sample or demo such as samples\minimal, and type
- 'make -f makefile.b32'. This produces a windows exe file
+ 'make -f makefile.b32'. This produces a windows exe file - by default
+ in the BORL subdirectory (see note 9)
+
4. For release versions, recompile wxWindows and samples using
'make -f makefile.b32 clean'
'make -f makefile.b32 FINAL=1'
6. You can use the WXUNIVERSAL widgets instead of the native MSW
ones (eg if you want to build an application with the same
look and feel on all platforms)
- Use the command
+ Use the command (in src\msw directory)
'make -f makefile.b32 WXUSINGUNIV=1'
Then run
'make -f makefile.b32 WXUSINGUNIV=1' in the sample directory which you wish
and do final releases by combinations of commandline parameters.
At the time of writing, (Oct 02) not all the wxDialogs are working
-7. To make console mode applications with wxWindows functions go
+7. To use UNICODE for win2000 and XP systems edit wxWindows\wx\include\msw\setup.h
+ so that wxUSE_UNICODE is 1 instead of the default value of zero
+
+8. To make console mode applications with wxWindows functions go
to the src\msw directory
'make -f makebase.b32 clean'
'make -f makebase.b32'
There is a sample\console directory and in this type
'make -f makefile.b32 wxUSE_GUI=0'
+9. OUTPUTDIR may be set to the name of the directory where you want all the
+ object files to be generated (the library files are always created in
+ %WXWIN%\lib). Compilation will fail if you set it to an empty string
+ to create them in the same directory as the source. If you change OUTPUTDIR,
+ make sure that it does not have a trailing backslash!
+ In the samples, you may use EXEDIR=adir to build the samples in adir. Setting
+ EXEDIR=. will build in the current directory,
+
Note (0): This provides the ability to produce separate wxwindows libraries
for different purposes, and only have to rebuild the applications
-
Note (1): the wxWindows makefiles assume byte structure alignment. Please
make sure that your own project or makefile settings use the
same alignment, or you could experience mysterious crashes. To
2. You can use the process_sample_bcb.bat command which is in
wxwindows\distrib\msw to generate a .mak or .bpr file for most of the
- samples [mak for Cbuilder 1-3; bpr for v4]. Execute this in the sample
- directory, passing the name of the cpp files on the command line. For more
- details, see the instructions in docs/tech/tn0004.htm or
- http://biolpc22.york.ac.uk/wx/bc/ide.html.
+ samples [mak for Cbuilder 1-6; v4 and after will convert this to bpr].
+ Execute this in the sampledirectory, passing the name of the cpp files
+ on the command line. For more details, see the instructions in
+ docs/tech/tn0004.htm or http://biolpc22.york.ac.uk/wx/bc/ide.html.
Borland 16 Bit compilation for Windows 3.1
------------------------------------------
- OUTPUTDIR may be set to the name of the directory where you want all the
object files to be generated (the library files are always created in
- %WXWIN\lib). You may set it to nothing to create them in the same directory
- as the sourcse, however using a separate directory is preferable if you use
- several different compilers. If you change OUTPUTDIR, make sure that it is
- either empty or has a trailing backslash!
+ %WXWIN%\lib). Compilation will fail if you set it to an empty string
+ to create them in the same directory as the source. If you change OUTPUTDIR,
+ make sure that it does not have a trailing backslash!
+
+- In the samples, you may use EXEDIR=adir to build the samples in adir. Setting
+ EXEDIR=. will build in the current directory,
Note (1): if your installation of Watcom doesn't have odbc32.lib file and
gives up. So the date/time option is switched off for Watcom C++.
Also, wxAutomationObject is not compiled with Watcom C++ 10.
-Note (3): if Watcom can't read the precompiled header when building a sample,
+Note (3): RawBitmaps won't work at present because they use unsupported template
+ classes
+
+Note (4): if Watcom can't read the precompiled header when building a sample,
try deleting src\msw\watcom.pch and compiling the sample again.
from e.g. the MinGW distribution, to a directory in your path.
-Symantec C++ compilation
+Symantec & DigitalMars C++ compilation
------------------------
-
-1. Make sure your WXWIN variable is set, and uses the FAT (short
+The DigitalMars compiler is a free succssor to the Symantec compiler
+and can be downloaded from http://www.digitalmars.com/
+
+1. You need to download and unzip in turn (later packages will oevrwrite older files)
+ Digital Mars C/C++ Compiler Version 8.33
+ Basic utilities
+ beta test C++ Compiler Version 8.34
+ from http://www.digitalmars.com/download/freecompiler.html [02 may 03, CE]
+
+2. Make sure your WXWIN variable is set, and uses the FAT (short
name) form.
-2. Edit setup.h and set wxUSE_DRAG_AND_DROP to 0.
+
3. Change directory to wx\src\msw. Type 'make -f makefile.sc' to
make the wxWindows core library.
4. Change directory to wx\samples\minimal and type 'make -f makefile.sc'
- to make this sample.
+ to make this sample. The mdi and image sample also work; others may give
+ linker erros due to missing libraries
-Note: the minimal sample doesn't link properly ('Error: no
-start address').
-32-bit compilation only (partially) supported at present, using SC++ 6.1.
-Some functionality is missing using this compiler (see makefile).
-Add -D__WIN95__ if your SC++ has Windows 95 support, and ignore
-Step (2). 16-bit compilation is left as an exercise for the user!
+16-bit compilation is no longer supported.
Salford C++ compilation
projects / wxWidgets.git / blobdiff