+Compiling using the makefiles (updated 24 Sept 02):
+
+1. Make sure your WXWIN variable is set [e.g add
+ set WXWIN=c:\wxwindows
+ to your autoexec.bat file], The WXWIN variable should contain neither spaces nor -
+ 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
+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. This produces a library wx32s.lib eliminating
+ all debugging information - if you wish to retain reduced debugging information
+ 'make -f makefile.b32 clean'
+ 'make -f makefile.b32 FINAL=hybrid'
+
+5. To make and use wxWindows as a DLL, type
+ 'make -f makefile.b32 clean'
+ 'make -f makefile.b32 DLL=1'
+ which generates a DLL (wx32d.dll) and import library (wx32d.lib),
+ and then for each sample,
+ 'make -f makefile.b32 WXUSINGDLL=1'
+ Please note that the samples have not been exhaustively tested
+ with this configuration. You may also generate a sepratae library
+ and second DLL using the commands
+ 'make -f makefile.b32 clean'
+ 'make -f makefile.b32 DLL=1 FINAL=1'
+ which generates a DLL (wx32.dll) and import library (wx32.lib),
+ and then for each sample,
+ 'make -f makefile.b32 WXUSINGDLL=1 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 (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
+ to build using the wxUniversal widgets. Use 'SET WXTHEME=GTK' [or WIN32 or METAL]
+ to test the existing themes
+ The makefile is written with the intention that you can build DLLs
+ and do final releases by combinations of commandline parameters.
+ At the time of writing, (Oct 02) not all the wxDialogs are working
+
+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'
+
+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
+change the alignment, add a suitable option to the $(CFG) target code
+in src/msw/makefile.b32.
+
+Note (2): 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 (3): 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: [Borland C++ 5.0, not Cbuilder]
+
+1. Load src\bc32.ide from the file bc32.zip at
+ http://biolpc22.york.ac.uk/pub/ports/bcc32/wxwin21/ and select 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.
+
+** REMEMBER **
+
+In all of your wxWindows applications, your source code should include
+the following preprocessor directive:
+
+#ifdef __BORLANDC__
+#pragma hdrstop
+#endif
+
+(check the samples -- e.g., \wx2\samples\minimal\minimal.cpp -- for
+more details)
+
+
+Borland C++Builder IDE compilation
+----------------------------------
+
+1. Build the wxWindows libraries using the Borland make utility as
+ specified in the section called "Borland C++ 5.0 compilation"
+ above. (C++ Builder includes a stand-alone C++ compiler. For example,
+ C++ Builder 4.0 comes with C++ 5.4.)
+
+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-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.
projects / wxWidgets.git / blobdiff