wxHatch Reference: Paths

Paths can be added to the wxhatch window using Choose | Select Additional Path. The selection may be used  in this session only, or saved in the registry. If saved, it can be associated with a partular compiler and restored when that compiler is selected (useful for the compilers' bin directory). This means you don't have to have the compiler's path added to the windows environment. Alternatively a path may be restored every time wxhatch starts, useful eg for cvs or other tools. The dialog allows you to add several paths, and add them all to the start path

The start path plus any additional paths will be applied to all children spawned by the wxhatch program, compilers, debuggers, tools, shells, etc

If the Watcom or Visual C compiler is detected, the children will also acquire the requisite INCLUDE and LIB environment settings.  With Visual C 2003 /2005  the compiler and SDK are usually in separate places, so use Choose | Add Path to add these directories (or equivalent installation directories)

For VS 2003:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin
C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin
For VS 2005
C:\Program Files\Microsoft Visual Studio 8\VC\BIN
C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin
For Watcom and VC6, the compiler and SDK share the same directory tree, so you only need the compiler directory in your Path:

When wxHatch is run in a cygwin/msys environment, or the path to their bin directory is added, all subsequent commands will be executed in a new bash shell with the path having / directory separators

wxHatch Home