Bitmap updates

[wxWidgets.git] / BuildCVS.txt

diff --git a/BuildCVS.txt b/BuildCVS.txt
index 5fe2d69624a9d99ce12f1b48f544f93c02971de7..7c14fd12cec91ddb4bfc4f3fc6a73cc7904a5958 100644 (file)
--- a/BuildCVS.txt
+++ b/BuildCVS.txt
@@ -72,6 +72,17 @@ c) Build instructions
 -> type: make -f makefile.g95  (if using GNU tools)
 or type: nmake -f makefile.vc   (if using MS VC++)
 
+d) Borland (including free command line tools)
+   Download tools from http://www.borland.com/downloads/
+   
+   See docs/msw/install.txt for details; in brief
+
+-> type set WXWIN=c:\wxwindows
+-> type set BCCDIR=c:\progra~1\borland\cb4
+-> type cd %WXWIN%\include\wx
+-> type copy msw\setup0.h setup.h
+-> type cd %WXWIN%\src\msw
+-> type make -f makefile.b32
 
 II) Unix ports
 --------------
@@ -125,11 +136,15 @@ Refer to the readme.txt and install.txt files in docs/mac to build
 wxWindows under Classic Mac OS using CodeWarrior.
 
 If you are checking out the CVS sources using cvs under Mac OS X and
-compiling under Classic Mac OS, make sure that all text files have a
-Mac OS type of 'TEXT' otherwise CodeWarrior may ignore them. Checking
-out the CVS sources using cvs under Mac OS X creates untyped files
-which can lead to compialtion errors under CodeWarrior which are hard
-to track down.
+compiling under Classic Mac OS:
+
+- make sure that all text files have a Mac OS type of 'TEXT' otherwise
+  CodeWarrior may ignore them. Checking out the CVS sources using cvs
+  under Mac OS X creates untyped files which can lead to compilation
+  errors under CodeWarrior which are hard to track down.
+
+- convert the xml files to CodeWarrior binary projects using the supplied
+  AppleScript in docs/mac (M5xml2mcp.applescript for CodeWarrior 5.3)
 
 V) MacOS X using configure and the Developer Tools
 ----------------------------------------