User's Guide: preTools Suite for Windows

Getting Started


Quick Installation

preTools are easily installed by following these steps:

  1. Copy required files to a directory in the system path.
    Each preTool is installed by copying the exe program file and its corresponding xml configuration file to a directory in the system or user PATH. The binary distribution contains the following pairs of files that you may choose to install:
    premake.exe and premake.xml
    prebuild.exe and prebuild.xml
    prevcbld.exe and prevcbld.xml

  2. Review the list of pre-configured build components. The preTools configuration files contain base configurations for these components.

    preMake's preconfigured build components
    Visual C++ 4.x Visual Studio .NET (7.0)
    Visual C++ 5.0 Visual Studio .NET 2003 (7.1)
    Visual C++ 6.0 Visual Studio .NET 2005 (8.0)
    Visual C++ 7.1 .NET Framework
    Visual C++ 8.0 .NET SDK 1.1
    Windows DDK 3790.1830 .NET SDK 2.0

    preBuild's preconfigured build components
    Windows DDK 2600 Windows DDK 2600.2106
    Windows DDK 3790 Windows DDK 3790.1830
    Windows WDK 5384 (Beta 2)  

    preVCbld's preconfigured build components
    Visual Studio .NET (7.0) Visual C++ 7.1
    Visual Studio .NET 2003 (7.1) Visual C++ 8.0
    Visual Studio .NET 2005 (8.0) .NET Framework
    .NET SDK 1.1 .NET SDK 2.0

  3. Detect required build components.
    Open a console window and execute the command:
    preMake -detect
    preBuild -detect
    preVCbld -detect
    and verify the 'found' status of each required build component. Build components which are not required may be listed as 'not found' or 'not defined' .

  4. Verify configurations.
    Verify the configuration you will use by issuing the command:
    premake -cfg:<cfgname> -noexec
    prebuild -cfg:<cfgname> -noexec
    prevcbld -cfg:<cfgname> -noexec
    This command will process the base_config and setup sub-elements under the named configuration and then dump the environment using the shell's set  command.

  5. Use a preTool in place of its Microsoft Tool.
    Use preMake.exe wherever you would use Nmake.exe.
    Use preBuild.exe wherever you would use Build.exe.
    Use preVCbld.exe wherever you would use VCBuild.exe.

    A typical preMake command line would be:
    premake -cfg:vc8 -debug -a -f myapp.mak
    The command options -cfg:vc8 -debug are consumed by preMake, while -a -f myapp.mak are passed through to Nmake unchanged.

    A typical preBuild command line would be:
    prebuild -cfg:wxpdrvr3 -checked -cef
    The command options -cfg:wxpdrvr3 -checked are consumed by preBuild, while -cef is passed through to Build unchanged.

    A typical preVCbld command line would be:
    prevcbld -cfg:vc8 /rebuild myapp.vcproj
    The command option -cfg:vc8 are consumed by preVCbld, while /rebuild myapp.vcproj is passed through to VCBuild unchanged.

    See the Command Options Reference topic for a description of all available command line options.