The first thing you need to do is edit the bin\set-vars.bat batch file to reference the location where you have installed the files, and the locations where all your compilers are installed. See the comments in set-vars.bat for more information.
Once you have the startup file configured, you then need to run the following each time you start a command shell to enable the SciTech makefile utilities (a good idea to put into your startup batch files):
call c:\scitech\bin\set-vars.bat
call c:\scitech\bin\wc11-w32.bat
The second batch file sets up the compiler configuration for your default compiler. The line above sets up for Watcom C++ 11.0 32-bit Windows compilation. Substitute this for any of the batch files in the bin directory for the compiler you are using. You can choose from the following batch files to configure the build environment for different supported compilers:
32-bit DOS protected mode support: |
|
bc45-d32.bat |
Borland C++ 4.52 (DPMI32) |
bc50-d32.bat |
Borland C++ 5.0 (DPMI32) |
bcb50-d32.bat |
Borland C++ Builder 5.0 (DPMI32) |
gcc2-dos.bat |
GNU C++ 2.9.5 (DJGPP 2.02) |
w10ad32.bat |
Watcom C++ 10.0a (DOS4GW) |
wc10-d32.bat |
Watcom C++ 10.6 (DOS4GW) |
wc11-d32.bat |
Watcom C++ 11.0 (DOS4GW) |
32-bit Windows GUI support: |
|
bc45-w32.bat |
Borland C++ 4.52 GUI programs |
bc50-w32.bat |
Borland C++ 5.0 GUI programs |
bcb50-w32.bat |
Borland C++ Builder 5.0 GUI programs |
gcc2-w32.bat |
GNU C++ for Win32 (Cygwin) GUI programs |
vc40-w32.bat |
Microsoft Visual C++ 4.2 GUI programs |
vc50-w32.bat |
Microsoft Visual C++ 5.0 GUI programs |
Vc60-w32.bat |
Microsoft Visual C++ 6.0 GUI programs |
wc10aw32.bat |
Watcom C++ 10.0a GUI programs |
wc10-w32.bat |
Watcom C++ 10.6 GUI programs |
wc11-w32.bat |
Watcom C++ 11.0 GUI programs |
32-bit Windows console support: |
|
bc45-c32.bat |
Borland C++ 4.52 console programs |
bc50-c32.bat |
Borland C++ 5.0 console programs |
bcb50-c32.bat |
Borland C++ Builder 5.0 console programs |
gcc2-c32.bat |
GNU C++ for Win32 (Cygwin) console programs |
vc40-c32.bat |
Microsoft Visual C++ 4.2 console programs |
vc50-c32.bat |
Microsoft Visual C++ 5.0 console programs |
Vc60-c32.bat |
Microsoft Visual C++ 6.0 console programs |
wc10aw32.bat |
Watcom C++ 10.0a console programs |
wc10-c32.bat |
Watcom C++ 10.6 console programs |
wc11-c32.bat |
Watcom C++ 11.0 console programs |
Note also that once you have properly set up the makefile utilities, you can switch between different compilers from the command line simply by calling one of the above batch files. This makes it easy to test and compile your own code with multiple compilers on a single machine.
For Windows development, you may also wish to note that the difference between console and GUI compilation is controlled by the WIN32_GUI environment variable. If you find that compiling SDK examples cannot be completed due to missing references to WinMain or DEF definition file, it is probably because that example is simply a console-only application. So try re-compiling with the “c32” version batch file instead of “w32”.
Copyright © 2002 SciTech Software, Inc. Visit our web site at http://www.scitechsoft.com