--- a/nt/README	Mon Aug 13 10:29:43 2007 +0200
+++ b/nt/README	Mon Aug 13 10:30:37 2007 +0200
@@ -14,25 +14,36 @@
 
 1.  You will need Visual C++ V4.2 or later to compile everything. Personally we
     have tested V4.2 and V5.0.
-2.  Grab the latest XEmacs beta from ftp.xemacs.org if necessary. All Win32
-    support is in the nt/ subdirectory.
-3.  Edit the xemacs.mak file and ensure variables point to the correct place.
     Note that Visual C++ assumes a couple of environment variables INCLUDE and
     LIB to be set which specify the location of the includes and libraries.
     At this point you can select X or Win32 native support.
-4.  Run make. I simply use nmake -f xemacs.mak. This will build temacs, the
-    DOC file, if startup.elc does not exist it will update the elc's and
-    then it will dump xemacs.
-5.  The build process creates debugging and "Source Browser" information for
-    use with MS DevStudio. To use this create a new "console" project and set
-    the Project/Settings/Debug executable name to the full path of
-    src\xemacs.exe. Remember to close the Source Browser file in DevStudio
-    before rebuilding.
-6.  If you're going to edit sources I recommend that you first get a copy of
-    makedepend and make a list of dependencies in the makefile by doing
-    "nmake -f xemacs.mak depend". I (jhar) have a hacked-up copy of X11R5
-    makedepend which I can distribute if anyone wants it. Is there a real
-    version anywhere which handles '\' as the path delimiter?
+2.  Grab the latest XEmacs beta from ftp.xemacs.org if necessary. All Win32
+    support is in the nt/ subdirectory. You'll also need the xemacs-base
+    package from the binary-packages subdirectory and you'll probably alsi
+    want at least the edit-utils, text-utils, cc-mode and prog-utils packages.
+    Unpack the packages into, say, c:\src\xemacs\packages.
+
+If you want to build for native GUI:
+
+1.  If you want XPM and toolbar support grab the latest version of the xpm
+    sources (xpm-3.4k.tar.gz at time of writing) and unpack it.
+    Copy nt/xpm.mak from the xemacs distribution to the lib subdirectory of
+    the xpm distribution, cd to that directory and build xpm with
+   `nmake -f xpm.mak`.
+2.  cd to the nt subdirectory of the xemacs distribution and build xemacs:
+    `nmake -f xemacs.mak HAVE_MSW=1 PATH_PACKAGEPATH="c:/src/xemacs/packages"`,
+    replacing "c:/src/xemacs/packages" with the location of your packages. Note
+    the double quotes and *forward* slashes in that path.
+    If you're building with XPM support, add this to the nmake command line:
+    `HAVE_XPM=1 XPM_DIR=x:\location\of\your\xpm\source\tree`.
+    Nmake will build temacs, the DOC file, update the elc's and dump xemacs.
+3.  The build process creates debugging and "Source Browser" information for
+    use with MS DevStudio. To use this create a new "console" project and
+    under Project/Settings set:
+	Debug: executable name = full path of src\xemacs.exe
+	Link: output file name = full path of src\temacs.exe
+	Browse Info: browse info file name = full path of src\temacs.bsc
+    Remember to close the Source Browser file in DevStudio before rebuilding.
 
 If you want support for X you will need:
 
@@ -45,6 +56,9 @@
     nt/X11.patch in the xc/lib/X11 directory which will fix the DLL definition
     file. Once compiled and installed, you will need to apply the following
     patch to Xmd.h. This is messy and better solutions would be appreciated. 
+4.  Goto 2 under 'native GUI' above and also supply:
+    `HAVE_X=1 X11_DIR=x:\root\directory\of\your\X11\installation'
+    to the nmake command line.
 
 --- Xmd.h~	Thu Jun 08 23:20:40 1995
 +++ Xmd.h	Sun Mar 16 13:09:10 1997