+Compiling using the makefiles:
+
+0. If downloading from CVS, copy include\wx\msw\setup0.h to
+ include\wx\setup.h.
+1. Make sure your WXWIN variable is set, and uses the FAT (short
+ name) form if doing a 16-bit compile.
+2. Change directory to wx\src\msw. Type 'make -f makefile.b32' to
+ make the wxWindows core library. Ignore the warnings about
+ 'XXX' not found in library.
+3. Change directory to a sample or demo such as samples\minimal, and type
+ 'make -f makefile.b32'.
+4. For release versions, recompile wxWindows and samples using
+ 'make -f makefile.b32 clean'
+ 'make -f makefile.b32 FINAL=1'
+ for the library and samples.
+5. To make and use wxWindows as a DLL, type
+ 'make -f makefile.b32 clean'
+ 'make -f makefile.b32 DLL=1'
+ and then for each sample,
+ 'make -f makefile.b32 WXUSINGDLL=1'
+ Please note that the samples have not been exhaustively tested
+ with this configuration.
+
+Note (1): the wxWindows library and (some) samples compile in 16-bit mode
+using makefile.bcc, but at present the wxWindows resource system is switched
+off in this mode. See issues.txt for details.
+
+Note (2): unfortunately most samples won't link in 16-bit mode,
+because the automatic data segment exceeds 64K. The minimal
+sample links and runs, however.
+
+Note (3): 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
+change the alignment, add a suitable option to the $(CFG) target code
+in src/msw/makefile.b32.
+
+Note (4): if you get undefined _SQL... symbols at link time,
+either install odbc32.lib from the BC++ CD-ROM into your BC++ lib
+directory, or set wxUSE_ODBC to 0 in include\wx\msw\setup.h and
+recompile wxWindows. The same applies if compiling using the IDE.
+
+Note (5): BC++ 4.5 (not 5.0) trips up over jdmerge.c in the JPEG folder;
+you will therefore need to set wxUSE_LIBJPEG to 0 in setup.h and remove
+the jpeg target from src\msw\makefile.b32, and remove jpeg from
+src\makeprog.b32.
+
+Note (6): If using C++Builder 4 and above (BC++ 5.4 and above), change LINK=tlink32 to
+LINK=ilink32 in src\makeb32.env. You may also need to disable
+wxUSE_LIBJPEG because there is a conflict in the BC++ headers
+(actually this problem seems to have gone away with 5.5 and SP1).
+
+Note (7): If you wish debug messages to be sent to the console in
+debug mode, edit src\makeb32.env and change /aa to /Tpe in
+LINK_FLAGS.
+
+Compiling using the IDE files:
+
+1. Load src\bc32.ide (Release settings)
+2. Go to Options|Project... and specify the correct BC++ include and lib path for
+ your file structure.
+3. Press F9 to compile the wxWindows library.
+4. Load samples\bc32.ide.
+5. Go to Options|Project... and specify the correct BC++ include and lib path for
+ your file structure.
+6. Press F9 to compile the samples (build each node separately if
+ you prefer, by right clicking and choose Build Node).
+7. Run each sample: you may need to run from each sample's directory
+ since some (notably the wxHTML samples) look for files
+ relative to the working directory.
+
+Note (1): the samples project file contains a selection of
+samples, and not all samples. The remaining samples can be made
+with the makefiles. See also the demos hierarchy which doesn't
+have any BC++ project files yet.
+
+Note (2): to make the png, zlib, jpeg and tiff libraries (needed for
+some samples) you need to compile them with bc32.ide.
+
+Note (3): the debug version of the wxWindows library is about 40 MB, and the
+release version is around 5 MB.
+
+See also the file docs/tech/tn0007.txt for further instructions and details
+of how to create your own project files.
+
+Borland C++ 5.5 compilation
+---------------------------
+
+Before compiling wxWindows with Borland C++ 5.5, there are a few
+issues concerning the compiler installation:
+
+1. The compiler must be installed to a path that does not contain
+ spaces, such as c:\Borland\Bcc55 (in particular, do not install
+ it below "C:\Program Files").
+
+2. Make sure that you downloaded and installed the service pack 1
+ for Borland C++ 5.5. This SP1 can be downloaded from:
+ http://www.borland.com/devsupport/bcppbuilder/patches/#freecompiler55
+
+ IMPORTANT:
+ When installing SP1, make sure that you extract (UnZip) the files
+ to the directory where you installed Borland C++ 5.5 (e.g.,
+ c:\Borland\Bcc55) with the option "use folder names" selected.
+ This is necessary, to ensure that the files (mostly include files)
+ are extracted to the right directory.
+
+3. Create the following two files in the same directory where you
+ installed Borland C++ 5.5 (e.g., c:\Borland\Bcc55):
+
+ a. bcc32.cfg
+ text file containing the following two lines:
+ -I"c:\Borland\Bcc55\include"
+ -L"c:\Borland\Bcc55\lib"
+
+ b. ilink32.cfg
+ text file containing the following line:
+ -L"c:\Borland\Bcc55\lib"
+
+ (replace c:\Borland\Bcc55 with the actual path where you installed
+ Borland C++ 5.5)
+
+4. Add the borland BIN directory to your path (e.g., c:\Borland\Bcc55\bin),
+ and define the environment variable BCCDIR=<Borland C++ 5.5 path>
+ (e.g., set BCCDIR=c:\Borland\Bcc55)
+
+Compiling wxWindows:
+
+Once the compiler and its service pack are properly installed, you build
+wxWindows using the provided makefile.b32 in the src/msw directory:
+
+a. To build wxWindows in DEBUG mode:
+
+ cd c:\wx2\src\msw
+ make -f makefile.b32
+
+ (replace c:\wx2 with the actual path where you installed wxWindows)
+
+b. To build wxWindows in RELEASE mode:
+
+ cd c:\wx2\src\msw
+ make -f makefile.b32 FINAL=1
+
+ (if you had previously built wxWindows, you need to clean all of
+ the object and intermediate files. Before the above make command,
+ run: 'make -f makefile.b32 CLEANALL')
projects / wxWidgets.git / blobdiff