Online document ___________________________________________________________________________ Other utilities =========================================================================== HOW TO USE THIS FILE =========================================================================== This file has a table of contents and an index that refer to "pages" in this file. If your editor has a search facility, you can use it to search for the page numbers listed in either the table of contents or in the index. The phrase "Page n" (where n represents the actual page number) appears at the bottom left of the "page" it refers to. Thus, at the bottom of page 1, you'll find "Page 1" as the last item on that "page." CONTENTS ___________________________________________________________________________ Other utilities Report by external references (/RX) . . . . . . . . . . . . 27 BGIOBJ: Converting graphics drivers Report of module sizes and fonts . . . . . . . . . . . . 2 (/RS) . . . . . . . . . . . . 27 Adding the new .OBJ files to Report by class type (/RC) . 27 GRAPHICS.LIB . . . . . . . . . . 3 Report of unreferenced symbol Registering the drivers and names (/RU) . . . . . . . . . 28 fonts . . . . . . . . . . . . . 3 Verbose reporting (/RV) . . . 29 An example . . . . . . . . . . 4 Examples of how to use The /F option . . . . . . . . . 5 OBJXREF . . . . . . . . . . . . 29 Advanced features . . . . . . . 5 Example 1 . . . . . . . . . . 29 CPP: The preprocessor . . . . . . 9 Example 2 . . . . . . . . . . 29 CPP as a macro preprocessor . 10 Example 3 . . . . . . . . . . 29 An example . . . . . . . . . . 10 Example 4 . . . . . . . . . . 30 GREP: A text-search utility . . 11 OBJXREF error messages and Command-line syntax . . . . . 11 warnings . . . . . . . . . . . 30 GREP options . . . . . . . . . 12 Error messages . . . . . . . 30 Order of precedence . . . . 14 Warnings . . . . . . . . . . 30 The search string . . . . . . 14 PRJCFG: Configuration file Operators in regular utility . . . . . . . . . . . . . 31 expressions . . . . . . . . 15 PRJCNVT: Old projects for new . . 31 File specifications . . . . . 16 PRJ2MAK: From project file to MAKE Some GREP examples . . . . . . 16 file . . . . . . . . . . . . . . 32 Example 1 . . . . . . . . . 16 THELP: The Turbo Help utility . . 33 Example 2 . . . . . . . . . 17 Loading and invoking THELP . . 33 Example 3 . . . . . . . . . 17 Navigating THELP . . . . . . . 34 Example 4 . . . . . . . . . 17 THELP options . . . . . . . . . 35 Example 5 . . . . . . . . . 18 /C#xx (select color) . . . . 35 Example 6 . . . . . . . . . 18 /Fname (full path and name for Example 7 . . . . . . . . . 19 help file) . . . . . . . . . 36 Example 8 . . . . . . . . . 19 /H, /?, and ? (display help OBJXREF: The object module cross- screen) . . . . . . . . . . . 37 reference utility . . . . . . . 20 /Kxxyy (reassign hot key) . . 37 The OBJXREF command line . . . 20 /U (remove THELP from The OBJXREF command-line memory) . . . . . . . . . . . 38 options . . . . . . . . . . 21 /Wx,y,w,h (set the window size Control options . . . . . 21 and location) . . . . . . . . 38 Report options . . . . . . 23 TOUCH . . . . . . . . . . . . . . 38 Response files . . . . . . . . 24 TRANCOPY: A project transfer item Free-form response files . . 24 utility . . . . . . . . . . . . . 39 Project files . . . . . . . 24 TRIGRAPH: A character-conversion Linker response files . . . 25 utility . . . . . . . . . . . . . 39 Sample OBJXREF reports . . . . 25 Transfer macros . . . . . . . . . 40 Report by public names State macros . . . . . . . 40 (/RP) . . . . . . . . . . . 26 File name macros . . . . . 41 Report by module (/RM) . . . 26 Instruction macros . . . . 41 Report by reference (/RR) . 26 Running DOS commands . . . . . 46 i Transfer memory settings . . . 47 Named keys . . . . . . . . . . 50 Turbo Editor macros . . . . . . 47 Predefined editor commands . . . 51 TEMC command line . . . . . . . 47 Syntax . . . . . . . . . . . . . 48 Index 61 Key codes . . . . . . . . . . . 49 ii Borland C++ comes with a host of standalone utilities that you can use with your Borland C++ files or other modules. Several are documented in the Tools and Utilities Guide; others are documented here. ------------------------------------------------------- Name Description ------------------------------------------------------- Documented in the Tools and Utilities Guide IMPDEF Creates a module definition file IMPLIB Generates an import library IMPLIBW Windows application that generates an import library MAKE Standalone program manager TLIB Turbo Librarian TLINK Turbo Linker WinSight Windows message monitor Documented in this file BGIOBJ Conversion utility for graphics drivers and fonts CPP Preprocessor - 1 - GREP File-search utility OBJXREF Object module cross-referencer PRJCFG Updates options in a project file from a configuration file, or converts a project file to a configuration file PRJCNVT Converts Turbo C project files to the Borland C++ format PRJ2MAK Converts Borland C++ project files to MAKE files THELP Turbo Help utility TOUCH Updates file date and time TRANCOPY Copies transfer items from one project to another TRIGRAPH Character-conversion utility TEML/TEMC Turbo Editor Macro Language and Compiler ------------------------------------------------------- This file explains what each utility is and illustrates, with code and command-line examples, how to use them. =========================================================================== BGIOBJ: Converting graphics drivers and fonts =========================================================================== You can use BGIOBJ to convert graphics driver files and character sets (stroked font files) to object (.OBJ) files. Once they're converted, you can link them into your program, making them part of the executable file. This is in addition to the graphics package's dynamic loading scheme, in which your program loads graphics drivers and character sets (stroked fonts) from disk at run time. Linking drivers and fonts directly into your program is advantageous because the executable file contains all (or most) of the drivers and/or fonts it might need, and doesn't need to access the driver and font files on disk when running. However, linking the drivers and fonts into your executable file increases its size. To convert a driver or font file to a linkable object file, use the BGIOBJ.EXE utility. This is the simplified syntax: BGIOBJ source_file where source_file is the driver or font file to be converted to an object file. The object file created has the same file name as the source file, with the - 2 - extension .OBJ; for example, EGAVGA.BGI yields EGAVGA.OBJ, SANS.CHR gives SANS.OBJ, and so on. Adding the new ======================================================= .OBJ files to GRAPHICS.LIB You should add the driver and font object modules to GRAPHICS.LIB, so the linker can locate them when it links in the graphics routines. If you don't add these new object modules to GRAPHICS.LIB, you...
mek4test