[Vm-dev] [commit] r2277 - Info on the various cygwinbuild configurations, product, assert & debug.

[commits at squeakvm.org]

Author: eliot
Date: 2010-09-04 09:52:23 -0700 (Sat, 04 Sep 2010)
New Revision: 2277

Modified:
   branches/Cog/cygwinbuild/HowToBuild
Log:
Info on the various cygwinbuild configurations, product, assert & debug.


Modified: branches/Cog/cygwinbuild/HowToBuild
===================================================================
--- branches/Cog/cygwinbuild/HowToBuild	2010-09-04 16:05:56 UTC (rev 2276)
+++ branches/Cog/cygwinbuild/HowToBuild	2010-09-04 16:52:23 UTC (rev 2277)
@@ -11,15 +11,42 @@
      svn co http://www.squeakvm.org/svn/squeak/branches/Cog/platforms
      svn co http://www.squeakvm.org/svn/squeak/branches/Cog/src
      svn co http://www.squeakvm.org/svn/squeak/branches/Cog/cygwinbuild
+2a. If you want the whole kit and caboodle including the VMMaker image try e.g.
+     svn co http://www.squeakvm.org/svn/squeak/branches/Cog cogvm
+
 3. Open a cygwin bash shell, cd into the cygbuild directory and execute
      make
+
+   Caution: if you previously used the mingw gnutools approach, you probably
+   have a path to that 2.x gcc in your Windows PATH.  Make sure that 'which gcc'
+   evalautes to the cygwin gcc 3.4.x not the MinGW gcc 2.95.x (try gcc -v).
+
 4. At the end of this process you should have a brand new Croquet VM in the
-   cygwinbuild/build/vm folder (make sure you transfer Squeak.map along with it)
+   cygwinbuild/build/vm folder (make sure you copy Croquet.map along with it)
 
+3a. The cygwin makefile supports building three VM configurations, product,
+    assert and debug, building product by default.  The configurations are
+	product: stripped  & unstripped production VMs optimized at -O2 in
+		build/vm/Croquet.exe
+		build/vm/CroquetUnstripped.exe
+	assert: an unstripped VM that includes assertion checks optimized at -O1 in
+		buildast/vm/Croquet.exe
+	debug: an unstripped, unoptimized VM that includs assertion checks
+		builddbg/vm/Croquet.exe
+    Note that even the stripped production VM can be used for debug using the
+	unstripped VM to provide symbols, e.g.
+		U:\ gdb bin/Croquet.exe
+		...
+		(no debugging symbols found)
+		(gdb) file CroquetUnstripped.exe
+		(gdb) run trunk.image
 
-Caution: if you previously used the mingw gnutools approach, you probably have
-a path to that 2.x gcc in your Windows PATH.  Make sure that 'which gcc' in
-cygwin is the cygwin gcc 3.4.x not the MinGW gcc 2.95.x (try gcc -v).
+	In fact there is an additional VM alongside each Croquet VM, e.g.
+		build/vm/CroquetConsole.exe
+	This VM is a Windows "console" application which will run inside an MSDOS
+	console window.  When the I/O code in 
+		platforms/win32/plugins/FilePlugin/sqWin32FilePrims.c
+	supports it this VM will be able to read and write to stdin and stdout.
 
 
 3a. If you want to get the Cog VM simulator working you'll need to build the