Open Watcom Developer's Guide - HEAnet Mirror Service

More documents

Recommendations

Info

Introduction wsample wstrip wstub wtouch wv yacc the execution sampler, companion tool to the profiler. strip utility for detaching or attaching debug information and/or resources. stub program for DOS/4GW. a touch utility. the debugger (used to be called WVIDEO, hence the name). Watcom’s version of YACC used for building compilers/assemblers. As you can see, there’s a lot of stuff! Some of these projects contain specific documentation pertaining to them, usually located in a directory called ’doc’ or somesuch. For the most part, the truly uptodate and comprehensive documentation is the source code. 10 The bld directory
2 First Steps This chapter briefly describes the prerequisite steps necessary to build and/or contribute to the Open Watcom project — how to get the source code and how to set up the build environment. 2.1 Connecting up The most uptodate version of the Open Watcom source code lives on the Open Watcom Perforce server. It is possible to go straight to the Perforce repository but most people will find it much easier to get a source archive first. The source archives can be found at the Open Watcom web site, http://www.openwatcom.org/ along with latest information on Perforce setup. You will generally need a working installation of the previous release of Open Watcom C/C++ and some free disk space to burn (one gigabyte should do). The Open Watcom source tree can be located in any directory on any drive. After extracting the source archive you will find a very important batch file called setvars in your Open Watcom root directory. This will set up a bunch of necessary environment variables but first you’ll have to edit it to reflect your directory structure etc. It also contains the necessary Perforce settings. Now is the time to connect to Perforce. Again, most uptodate information can be found on the Open Watcom web site. If you followed the instructions correctly, no servers are down and no other unpredictable (or maybe predictable) things happened, you will have brought your source tree to the latest revision (aka tip or head revision). 2.2 Gearing up for Building Before you start building the Open Watcom tools proper, you will need to build several helper tools: builder, pmake, cdsay and a few others. These tools have to be built manually because the build process won’t work without them. The tools can be found in appropriately named subdirectory of the bld directory, which is named builder (showing complete lack of imagination). Gearing up for Building 11
Page 1 and 2: Open Watcom Developer’s Guide Fir
Page 3 and 4: Table of Contents Introduction ....
Page 5 and 6: Introduction
Page 7 and 8: 1 Project Overview This document se
Page 9 and 10: Project Overview The root of the Op
Page 11 and 12: Project Overview dwarf editdll emu
Page 13: Project Overview ui vi viper viprde
Page 17 and 18: Building
Page 19 and 20: 3 Build Architecture In an effort t
Page 21 and 22: Build Architecture $(AS): $(RC): $(
Page 23 and 24: Build Architecture 3.6 Memory Track
Page 25 and 26: Build Architecture tools required d
Page 27 and 28: Build Architecture 5. Add proj_name
Page 29 and 30: 4 Technical Notes 4.1 32-bit Window
Page 31 and 32: 5 Build Process We use the (Open) W
Page 33 and 34: 6 Testing There is undoubtedly a qu
Page 35 and 36: Testing orl plustest ssl trmem vipr
Page 37 and 38: Style
Page 39 and 40: 7 Programming Style Programming sty
Page 41 and 42: Programming Style functions the eff
Page 43 and 44: Documentation
Page 45 and 46: 8 Producing Documentation The purpo
Page 47 and 48: Producing Documentation • Note th
Page 49 and 50: Producing Documentation .np The rec
Page 51 and 52: Index # F #include 35 fastest 16-bi

Open Watcom Developer's Guide - HEAnet Mirror Service

Create successful ePaper yourself

Delete template?

Save as template?