Features
Downloads
News
Groups
Bugzilla
Faq-O-Matic
Status Report
Downloads
Mission
Statement
Setup for
Parallel Testing
MarkO's OS/2 Mirrors
Site
==============
OS/2 (tm) FAQ
UNDER CONSTRUCTION
==============
Open Watcom ForTran (WatFor)
Interim Distribution Page
Setup for Parallel Testing
WatFor was developed way before the IBM-PC® was
ever conceived, let alone Win32 and the Windows® Registry. Open
Watcom uses Environment Variables to select where the Include Files and
Configuration Files are located, and of course the PATH Environment
Variable to direct which Executables are used to build your project.
This makes setting up a Parallel Install of Open Watcom very easy, and
does not disrupt the currently installed Watcom or Open Watcom
Installation.
1) Determine what you want to call your
Parallel Install Directory. (e.g. If you Open Watcom directory is
"D:\WATCOM", a Parallel Directory name might be "D:\WATCOM12" or
"D:\WATCOM.DEV".)
2a) Re-Install Open Watcom 1.2 or 1.3
with the Full Installer, when prompted for Install Directory, chose the
Parallel Directory rather than the Current Directory. When
Prompted, "Do you want to update the environment automatically?",
select NO.
or
2b) Copy the Open Watcom 1.2 or 1.3
Compiler will ALL Subdirectories to the Parallel Directory.
3) Copy the ForTran Executables
and Support files from this web site into the appropriate locations in
your Parallel Install directory.
4) You will need to use the
SETVARS.BAT or SETVARS.CMD that is in the Parallel Install Directory to
use the Parallel Installed Compiler. Don't forget to CHANGE the
SETVARS.BAT or SETVARS.CMD if you used Method 2b above.
Setup for Perforce® Source Code Sync
(still under development)
Mat Nieuwenhoven and Mark Overholser, Open Watcom<-->Perforce
setup from openwatcom.fortran news group.
And I would like to add a few more step that I needed to get to where I
am, and still am "stumbling around in the dark", for the most part.
1. You install the Perforce (source control) client (see
www.openwatcom.org for details).
<http://www.openwatcom.org/support/perforce_content.html>
This is a complete adventure in itself.
If you are on OS/2, the Command Line Interface (CLI) is all you get, do
print out the Manual..
For Windows, there is an interactive program, turn on the "commands" in
the options section, so you get an idea of what you need to type for
the CLI version.
I don't remember other Reversion Control System (RCS) working quiet
like Perforce, I wish I could find the "Perforce Overview" on how it
has been envisioned to work for the programmer, rather than using
"trial and error".
2. Get access (mail Kendall Bennett).
You can Sync Up with Perforce using the "anonymous" login, but you can
not make additions.
3. Download and install the 1.2 source code, use a directory without
spaces in the path! You also need the 1.2 released compiler.
I need to "stress" FAT 8.3 naming convention, rather than just "without
spaces" This is the safest way to reduce problems in building Open
Watcom.
Watcom does not like spaces in the path names, if you are on Fat32 (and
I believe NTFS) there are ALWAYS FAT (8.3 naming convention) available.
On Win2000 a "dir /x" at the cmd prompt will give you the 8.3 names and
the VFAT names:
C:\>dir /x
Volume in drive C is WIN2K_SP3
Volume Serial Number is 1469-1A0B
Directory of C:\
06/25/2004 17:41
<DIR> FOUND.000
06/14/2004 18:59
<DIR> WINNT
06/14/2004 19:03
<DIR>
DOCUME~1 Documents and Settings
06/14/2004 19:03
<DIR>
PROGRA~1 Program Files
06/14/2004 20:15
<DIR> KBM
06/27/2004 19:26
<DIR>
J2SDK1~1.2_0 j2sdk1.4.2_04
06/14/2004 19:42
<DIR>
VIAHM
VIAhm
06/15/2004 00:06
<DIR> 4NT
06/15/2004 00:10
<DIR>
PRIMSTII
PriMstII
06/15/2004 00:13
<DIR> APPS
06/15/2004
19:41
5,953 CLDMA.LOG
1 File(s) 5,953
bytes
10 Dir(s) 1,539,192,832 bytes free
C:\>
So if you "insist" on installing Open Watcom Source files in "Documents
and Settings", use "DOCUME~1" to reference that subdirectory, and any
more beneath it in the path to your Open Watcom Source.
4. Change the setvars.bat file (or cmd file, or .sh script) to your
environment, and run it. Mostly, the P4 variables, and the location of
the
released 1.2 compiler.
I like to make a copy of the "setvars.???" because occasionally they
get updated on a Perforce Sync. Also you can have more than one
setvars.???, for testing different complier setups.
For testing purpose of "experimental compilers", you might Clone your
release 1.2 compiler, (Mine is in D:\DEV\OPENWC12) to an adjasent
directory (like in D:\DEV\OPENWC12.DEV) so that you could overwite
certian parts of the Open Watcom system, and leave the rest alone (like
copying and experimental ForTran compiler wfc.exe and wfc386.exe to
D:\DEV\OPENWC12.DEV\binnt, overwriting the release versions, with the
experimental versions, and leaving you release compiler (located in
D:\DEV\OPENWC12) alone so you still get some work done.
You would want different setvars.??? to access the different Open
Watcom compilers. An easy step to do, once you have got the first
one working.
5. Run the Perforce client to map the source view on the server to your
desired directory structure; it will remember your view.
Perforce seems quiet "flexible" in this aspect. The "depot" view,
can be "replicated identically" to your system, or you can have it
"relocate" various branches to other locations, on a machine by machine
basis.
6. Use the Perforce client to force a sync between the current
development 'had' and the 1.2 source.
7. Under the 'root' of your watcom source, there is a directory bld.
Goto bld\builder\nt386, and run wmake. This creates some utilities, one
of the is 'builder'.
Also go to bld\pmake\nt386 and run wmake, and then
bld\posix\systems\nt386 and run wmake. The makefiles should copy
the executables to a place on the Path.
8. Go back to up the bld directory, run 'builder rel2 os_nt' . This
will build everything for NT and put the executables in the rel2 subdir
below
the 'root'. Expect some errors on building the docs. If your machine is
fast, you can also do 'builder rel2' , which will build all host
platforms
(except Alpha and PPC). This takes approximately 4-5 hours on a 400 Mhz
Pentium, 1.5 hours on a 2GHz Athlon, depending on disk and memory.
My 950 MHz Duron with 1GB of memory running Win2000 SP3 takes about 2
hours.