readme_build_instructions.txt

虚拟打印机

FILE:  README_BUILD_INSTRUCTIONS.txt
       Michael H. Overlin
       Contact:  [e-mail]
       July 2006


1.  There are Visual Studio solution and project files.
    I only use them for editing, 
    and to do syntax checks on individual source files.

    I like the Visual Studio editor, so I got a copy of
    Visual C++ Express edition for free.  If you want a free copy you can
    also download it immediately from microsoft.  I also used it for debugging.
    At the time I installed the express edition there were instructions on the
    microsoft web site on how to make a few quick changes that allow you to
    build win32 executables, although the project options only support console
    applications.  I suspect you need to designate the projects to be win32 in order
    to compile an individual source file to syntax check it.  However, the express
    edition seems to be able to READ project and solution files generated by the
    full visual studio 8, with its much larger array of project types, so
    if you get the express edition you should be able to open these projects and use
    it as i did for editing and for syntax checking -- and for debugging.

    The PrintResizer.sln file contains project files for all of the different
    components, and all the different kinds of source files (makefiles, "source"
    files for the DDK build engine, etc.)

    I should also mention, if you want to modify or add dialogs or other resources
    you may want a visual windows resource editor.  I happened to have an 
    old copy of MS Dev Studio 5 that I used for this, there are probably
    free resource editors available.

2.  To actually do a build, you will need
    *  The MS Windows DDK (Device Driver Development Kit) for Windows 2000, windows XP,
       and Windows Server 2003 with Service Pack 1.  

       The DDK is free.  I ordered a copy on CD-ROM ( shipping was about $5 ), you
       may now be able to download it immediately.

       After I installed the DDK, when accessing the DOS-Shell build environments
       the version or build number for this DDK was indicated as    
       "3790.1830" .

    *  mscompress.exe which is a GnuWin32 version of a compression utility that used to 
       be available from Microsoft under the name "compress.exe"
       You can get it from sourceforge (do a google search or some kind of search to find
       it)

    *  As I said in (1) you don't need Visual C++ Express to build, 
       I just use it for editing, syntax checking, and debugging.

3.  Unfortunately building isn't a single command, there are a few steps.
    *  When I want to be sure a build is up to date I execute the batch file
       "clean.bat" located in the root directory.  The DDK build utility doesn't
       recognize the need to rebuild a resource ".res" file when a file included
       in the corresponding ".rc" file has changed, for example, and I don't know
       (have never checked) if adding "-cZ" as a parameter to the DDK's build command
       removes ".res" files -- it probably does.

    Steps:
    a.  Get a build environment by going to the Windows "Start->Programs->Development Kits"
        menu (latter installed when you install the DDK) and select the 
        Windows 2000 Checked build environment for a debugging build, or
        the Windows 2000 Free build environment for a release build.
        I use the windows 2000 envioronments to build for Windows NT 4.0, 2000, 2003 Server,
        and XP.  (at the moment the software has been successfully tested on windows
        2000 and XP, I'm confident it will work on 2003 and it may work on 4.0).

    b.  Once you have the DOS Shell build environment, change directory to
        the the root directory for the source.
    
    c.  execute the command "build"  (without quotation marks, obviously)  this 
        invokes the DDK build engine.

        this will build the following:
        printResizer.lib
        prgraphics.dll
        prui.dll
        prprint.dll
        pruninstaller.dll
        prpreview.exe

    d.  execute the command "update" if you are doing a checked (debug) build, or
        "updatefre" for a release build (these are ".bat" batch files)

    e.  execute the command "cd install\i386"
 
    f.  Now I assume that mscompress in in your path.  I put it in my WINNT\system32 directory.
        execute the command "mscompress *"

    g.  execute the command "cd ..\..\pruninstallerstub"

    h.  execute the command "build"

    i.  execute the command "cd .."

    j.  execute the command "update" if you are doing a checked (debug) build, or
        "updatefre" for a release build

    k.  execute the command "cd install\i386"
  
    l.  execute the command "mscompress  pruninstallerstub.exe"
  
    m.  execute the command "cd ..\..\prinstaller"

    n.  execute the command "build"

    This last command will create an executable named "prinstaller.exe" in either
    prinstaller\objchk_w2k_x86\i386 or in prinstaller\objfre_w2k_x86\i386 depending
    on whether you were using the checked or free build environments.

4.  In (3) were instructions to build the installer.  If you just
    want to build the software minus the installer and uninstaller, you can
    just execute "build" from the root source directory.

    I would often just do this, then use the Windows 2k "system services" control panel from
    "administrative tools" to stop the print spooler, and then use
    a batch file to copy all those dll's and executables to the
    spoolers printer driver directory for my system, and then restart the spooler.

    Visual c++ express debugger has the ability to attach to a process, so I could
    do a print and then attach to the preview utility application to debug it, or
    if i wanted to debug the printer driver dll's i could 
    attach to whatever process was about to use the dll's, for example to 
    ms wordpad if i was printing from ms wordpad.