Borland C++ build doesn't depend on Cygwin configure

[fw/sdcc] / doc / bccinst.txt

diff --git a/doc/bccinst.txt b/doc/bccinst.txt
index 76e722b1af9b354899880048f2ed6580caa5de38..a808722a084781d081d7999cdcb63606223e6ea1 100644 (file)
--- a/doc/bccinst.txt
+++ b/doc/bccinst.txt
@@ -1,20 +1,18 @@
 Building SDCC with Borland C++ under Windows
 
-1: Build SDCC under Cygwin as documented in cygwininst.txt (this is
-necessary in order to run all the necessary configuration steps).
-
-2: If necessary, modify support\gc\BCC_Makefile to point to your Borland
-C++ installation.
-
-3: From the sdcc directory, run the command "make -f Makefile.bcc". This
+1: From the sdcc directory, run the command "make -f Makefile.bcc". This
 should regenerate all the .exe files in the bin directory except for
 sdcdb.exe (which currently doesn't build under Borland C++).
 
-4: If you modify any source files and need to rebuild, be aware that the
+2: If you modify any source files and need to rebuild, be aware that the
 dependancies may not be correctly calculated. The safest option is to
 delete all .obj files and run the build again. From a Cygwin BASH
 prompt, this can easily be done with the commmand:
 
- 'find . -name "*.obj" -print | xargs rm'
+$ find . \( -name '*.obj' -o -name '*.lib' -o -name '*.rul' \) -print -exec rm {} \;
+
+or on Windows NT/2000/XP from the command prompt with the commmand:
+
+del /s *.obj *.lib *.rul
 
 from the sdcc directory.