X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/025bbf5bcf281a694804c0d7b397fddb51f933b3..768d9ec8ca53f44275a6250c44bb69bfc2840e8c:/docs/msw/install.txt

diff --git a/docs/msw/install.txt b/docs/msw/install.txt
index 0a3bc76ac8..1f18abb765 100644
--- a/docs/msw/install.txt
+++ b/docs/msw/install.txt
@@ -81,6 +81,9 @@ Cygwin/Mingw32 to quickly locate the instructions for your compiler.
 Microsoft Visual C++ compilation
 --------------------------------
 
+You may wish to visit http://wiki.wxwindows.org/wiki.pl?MSVC for a more
+informal and more detailed description of the process summarized below.
+
 Please note that the VC++ 6.0 project files will work for VC++ .NET also, but
 you must open the .dsp files and not the .dsw files and in this case you will
 need to manually build the other .dsp on which wxWindows.dsp depends: jpeg,
@@ -236,12 +239,16 @@ Compiling using the makefiles (updated 24 Sept 02):
    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
+  'make -f makefile.b32'. This produces a windows exe file - by default 
+   in the BORL subdirectory (see note 9)
+
 4. For release versions, recompile wxWindows and samples using
    'make -f makefile.b32 clean'
    'make -f makefile.b32 FINAL=1'
@@ -288,6 +295,14 @@ Compiling using the makefiles (updated 24 Sept 02):
    There is a sample\console directory and in this type
    'make -f makefile.b32 wxUSE_GUI=0'
 
+9. OUTPUTDIR may be set to the name of the directory where you want all the
+   object files to be generated (the library files are always created in
+   %WXWIN%\lib). Compilation will fail if you set it to an empty string 
+   to create them in the same directory as the source. If you change OUTPUTDIR, 
+   make sure that it does not have a trailing backslash!
+   In the samples, you may use EXEDIR=adir to build the samples in adir. Setting
+   EXEDIR=. will build in the current directory,
+
 Note (0): This provides the ability to produce separate wxwindows libraries
    for different purposes, and only have to rebuild the applications
 
@@ -394,7 +409,7 @@ There are several makefile variables which may be modified:
 
 - OUTPUTDIR may be set to the name of the directory where you want all the
   object files to be generated (the library files are always created in
-  %WXWIN\lib). Compilation will fail if you set it to an empty string 
+  %WXWIN%\lib). Compilation will fail if you set it to an empty string 
   to create them in the same directory as the source. If you change OUTPUTDIR, 
   make sure that it does not have a trailing backslash!