Open Watcom Developer's Guide - HEAnet Mirror Service

More documents

Recommendations

Info

Documentation 8.2 Building PostScript Documentation Here are the steps to formatting a book for printing on a PostScript printer. cd %doc_root%\ps wmake hbook= where is one of devguide c_readme cguide cguideq clib QNX) clibqnx cpplib ctools cw f77graph f_readme fpguide ftools fuguide guitool ide lguide pguide wd Developer’s Guide (this document) C/C++ Read Me First C/C++ User’s Guide C/C++ User’s Guide for QNX C Library Reference (for all systems except C Library Reference for QNX (stale) C++ Class Library Reference C/C++ Tools User’s Guide CauseWay User’s Guide F77 Graphics Library Reference F77 Read Me First F77 Programmer’s Guide F77 Tools User’s Guide F77 User’s Guide Graphical Tools User’s Guide IDE User’s Guide Linker User’s Guide C/C++ Programmer’s Guide Debugger User’s Guide The output file is of type .ps. You should be able to send this file to any PostScript printer or view it in GhostScript or convert it to PDF or do whatever it is you do with PostScript files. 8.3 Building Online Help Documentation For Microsoft Help format (old Windows 3.x help format): • Switch to the appropriate directory: cd %doc_root%\win • Run wmake to create all online help. 42 Building Online Help Documentation
Producing Documentation • Note that you must have the Microsoft Help Compiler (HC) installed. For Microsoft Help format ("new" Windows NT/95 help format): • Switch to the appropriate directory: cd %doc_root%\nt • Run wmake to create all online help. • Note that you must have the Microsoft Help Compiler (HCRTF) installed. For Watcom Help format (for the WHELP command): • Switch to the appropriate directory: cd %doc_root%\dos • Run wmake to create all online help. For OS/2 Help format: • Switch to the appropriate directory: cd %doc_root%\os2 • Run wmake to create all OS/2 online help. • Note that this will only work on an OS/2 system with the IBM IPF Compiler (IPFC) installed. To format one document at a time, go to the appropriate directory (for instance docs\os2 ) and run wmake with argument hbook= where is one of the online books listed above. 8.4 Editing the Documentation All the documentation is stored in ASCII text files with the file extension "GML". The files are annotated with a combination of Script and GML (Generalized Markup Language) tags. The Script tags are of the form ".tag" (i.e., they begin with a period and are followed by two or more letters or digits). Script tags will be most familiar to anyone who has ever used Editing the Documentation 43
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 and 14: Project Overview ui vi viper viprde
Page 15 and 16: 2 First Steps This chapter briefly
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: 8 Producing Documentation The purpo
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?