RTapo.com: Setting Up Borland's Free Command-line Tools

Downloads --- top ---

Borland C++ 5.5 Free Command-line Tools --- top ---
Register/log in, complete a survey, and finally download the Borland C++ 5.5 Free Command-line Tools (8.7 mb) at http://www.codegear.com/tabid/139/Default.aspx. Start out by clicking on 'Compiler'.
Turbo Debugger --- top ---
The optional Turbo Debugger (590 Kb) can be obtained at http://www.codegear.com/tabid/139/Default.aspx. Click on 'Turbo Debugger'.
IDE Development Tools --- top ---
Below are two optional, free tools that provide ide support for Borland C++ 5.5 Free Command-line Tools. If an ide is not used, a source editor like EditPlus, PSPad, or even NoteTab Light 4.95 is recommended.
- VIDE: Download http://prdownloads.sourceforge.net/vgui/vide2setup.exe (2.8 mb)
  VIDE is an Integrated Development Environment with support for Borland C++ 5.5 Free Command-line Tools, including the Turbo Debugger. Supports other compilers and languages as well. It supports the free Windows resource editor, from the LCC-Win32 compiler, and can convert or generate makefiles for simple projects.
- Visual Windows for BC++: Download http://phys.cool.ne.jp/BC/bcwe06-212S.exe (8.3 mb, includes the Command-line Tools), -or- http://phys.cool.ne.jp/BC/bcwe06-212.exe (1.4 mb, does not include Command-line Tools)
  Visual Windows for BC++ Ver.2006-2.12 (Updated 2006/08/20) provides an integrated programming environment for Borland C++ 5.5 Free Command-line Tools 5.5. It supports console programs, Window programs (no tool for designing dialog layout), and Windows DLL programs. Detects the presence of Turbo Debugger and automatically creates a debug-oriented executable if present.

Documentation --- top ---

Compiler And Command-line Tools Documentation
- Help files for the Command Line Tools (7.7 mb) ftp://ftp.borland.com/pub/bcppbuilder/techpubs/bcb5/b5std.zip
  * Below is a list of help files in the b5std.zip bundle that are useful/relevant to the Command Line Tools.
  Much of the material in the b5std.zip bundle is related to the C++ Builder IDE.
  - BCB5TOOL.HLP Tools Overview
  - BCB5SCL.HLP Standard C++ Library: Class Reference
  - BCB5ERRS.HTP About Error And Warning Messages
  - BCB5LANG.HLP Lexical Elements
  - BCB5DAP.HLP Working With Sockets
- Win32 API Help (8 mb) ftp://ftpc.borland.com/pub/delphi/techpubs/delphi2/win32.zip - alternate - ftp://ftp.cs.virginia.edu/pub/lcc-win32/win32hlp.exe
- External Installation And Setup Tutorials

Turbo Debugger Documentation
- Turbo Debugger Help http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-help
- Command Line Switches http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-cmdline
- Keyboard Command Shortcuts http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-keys

VIDE Documentation
- The Borland C++ Compiler 5.5 with The VIDE http://www.objectcentral.com/vide/help/videdoc/bcc32.html
- The VIDE User Guide http://www.objectcentral.com/vide/help/videdoc/videdoc.htm
- Quick Start Guide http://www.objectcentral.com/vide/help/videdoc/videquickstart.htm
- Command Reference http://www.objectcentral.com/vide/help/videdoc/videcmds.htm
- Editor Reference http://www.objectcentral.com/vide/help/videdoc/videedit.htm
- C/C++ Tutorial http://www.objectcentral.com/vide/help/videdoc/videcpp.htm
- Links to the original source of the various documents formerly contained in the VIDE Help System http://www.objectcentral.com/vide/help/vhelp.htm

Visual Windows for BC++ Documentation
- Visual Windows for BC++ Help Files http://phys.cool.ne.jp/BC/bcwehlp.zip (86 kb)

Installation --- top ---

Compiler, And Command-Line Tools Installation --- top ---
To install Borland's Free Command-line Tools, click on the name of the file ( FreeCommandLineTools.exe ) and follow the steps in the installation process. If the default options are used (recommended), the directory structure, and files, will be copied to C:\Borland\BCC55
Turbo Debugger Installation --- top ---
To install the Turbo Debugger, click on the name of the file ( TurboDebugger.exe ), and follow the installation process. Extract the debugger files into the Borland C++ 5.5 directory (default: C:\Borland\BCC55).
VIDE Installation --- top ---
To install the VIDE development environment, click on the name of the file ( vide2setup.exe ) and follow the steps in the installer's installation process. The default directory structure, and files, location will be C:\Program Files\Vide
Visual Windows (BC++) Installation --- top ---
To install Visual Windows (BC++), click on the file name ( bcwe06-212.exe - or - bcwe06-212S.exe ) and follow the steps in the installation process. Using the default options, the directory structure, and files, will be copied to C:\Program Files\BccWinUs. If package bcwe06-212S.exe is installed, (the one with the Command-line Tools) by default, the Command-line Tools directory structure, and files, will be copied to C:\Borland\BCC55

Configuration --- top ---

Compiler, And Command-Line Tools Configuration --- top ---

To correctly configure Borland's Free Command-line Tools, complete the four tasks listed below.

Edit The System Path: Add the Borland\Bcc55\Bin directory and the Borland\Bcc55\Include directory to the system path.
Edit Compiler Configuration File: Create bcc32.cfg, the compiler configuration file.
Edit Linker Configuration File: Create ilink32.cfg, the linker configuration file.
Edit Platform Configuration File: Create win32.cfg, the system configuration file.

Instructions for completing these tasks are provided below.

Edit The System Path --- top ---
- Windows 95/98/ME Instructions
  
  Open the file C:\AutoExec.bat in a text editor for editing. Add the following two lines to the AutoExec file.
  
  SET PATH=%PATH%;C:\Borland\Bcc55\Bin;C:\Borland\Bcc55\Include
  SET INCLUDE=C:\Borland\Bcc55\Include
  
  Save C:\AutoExec.bat, and close the file. These entries enable the operating system to find the Command-line Tools and their required files. These changes will become effective after restarting the system.
- Windows NT/2000/XP Instructions
  
  Open the System Properties dialog, from the Control Panel. Select the Advanced tab, and then click on the Environmental Variables button at the bottom. In the System Variables section of the Environmental Variables panel, highlight the Path variable and click on the Edit button at the bottom. Append the following, as is, to the end of the existing path.
  
  ;C:\Borland\Bcc55\Bin;C:\Borland\Bcc55\Include
  
  In the System Variables section of the Environmental Variables panel, highlight the INCLUDE variable and click on the Edit button at the bottom. Append the following, as is, to the end of the existing INCLUDE path.
  
  ;C:\Borland\Bcc55\Include
  
  If the INCLUDE variable does not exist in the list of System Variables, click on the New button at the bottom. Create the INCLUDE variable, and assign it the path to the borland include directory.
  
  C:\Borland\Bcc55\Include
  
  These changes will take affect after restarting the system.

Edit Compiler Configuration File bcc32.cfg --- top ---

Create a blank new document in a text editor. Add the following entries to the empty document.

-I"c:\Borland\Bcc55\include"
-L"c:\Borland\Bcc55\lib;c:\Borland\Bcc55\lib\psdk"
-P
-v-
-w
-DWINVER=0x0400
-D_WIN32_WINNT=0x0400

Save the document as C:\Borland\BCC55\Bin\bcc32.cfg

Here are definitions for the compiler options.

-I	tells the compiler where to look for system include files
-L	tells the compiler where to look for libraries
-P	tells the compiler to compile using C++, even if the source ends with .c
-v-	tells the compiler to turn off debugging
-w	tells the compiler to issue warnings
-D	optional defines enabling executables to work with Windows NT4, 95, and 98. (bcc32 targets Windows 2000 by default.)

The options specified in bcc32.cfg define the default compiler behavior. If different default behavior is required, then make modifications to bcc32.cfg. For a list of available compiler options, type bcc32 at the command line, or reference the BCC32.EXE Switches reference at objectcentral.com. Note: Options passed to the compiler at runtime have precedence over options in the configuration file.

Edit Linker Configuration File ilink32.cfg --- top ---

Create a blank new document in a text editor. Add the following entries to the empty document.

-v-
-x
-L"c:\Borland\Bcc55\lib;c:\Borland\Bcc55\lib\psdk"

Save the document as C:\Borland\BCC55\Bin\ilink32.cfg

Here are definitions for the linker options just specified.

-v- tells the linker to turn off debugging (right side minus sign negates the switches normal behavior)

-x tells the linker not to generate a map file

-L tells the linker where to look for libraries

Options defined in the ilink32.cfg configuration file define the linker's default behavior. Edit ilink32.cfg to modify default linker behavior. Type ilink32 at the command line, or consult Bruce Wampler's ILINK32.EXE Switches reference at objectcentral.com, to see all available options for the ilink32 linker. Note: Options passed to ilink32.exe at runtime have precedence over options in it's configuration file.

Edit Platform Configuration File win32.cfg --- top ---

What follows is optional. It is needed for executables to run reliably on Windows NT 4.0, or Windows 95, or Windows 98. (bcc32 targets Windows 2000 platform and higher by default.)

Create a blank new document in a text editor. Add the following entries to the empty document.

-DWINVER=0x0400
-D_WIN32_WINNT=0x0400

Save the document as C:\Borland\BCC55\win32.cfg

-v-	tells the linker to turn off debugging (right side minus sign negates the switches normal behavior)
-x	tells the linker not to generate a map file
-L	tells the linker where to look for libraries

Reference 1BCC32.EXE Switches, ILINK32.EXE Switches, BCC32 Libraries, Windows Header File Macros

Turbo Debugger Configuration --- top ---
The td32 debugger can be configured with td32inst, it's configuration utility. Open a dos prompt, and type, td32inst, then hit [enter]. If the mouse is not working, key [ALT-Enter], to toggle full screen mode (mouse will work in full screen mode). Several display preferences, and debugging options can be configured by this utility, which will store the information in the file TDCONFIG.TD2. Be sure to save any changes made before exiting the utility.
VIDE Configuration --- top ---
To correctly configure VIDE to work with the Borland C++ 5.5 Free Command-line Tools, begin by including the VIDE installation directory in the system path. If VIDE is installed to it's default location, just add C:\PROGRA~1\VIDE or "C:\Program Files\Vide" to the system path. See Edit The System Path in this document, for instructions on how to edit the system path.

Next, VIDE editor options need to be configured. Run the VIDE editor, and click on the 'Options' menu, then select 'VIDE' (Options->VIDE). A dialog like the one in Fig. 1 should appear.

Fig. 1: VIDE Preferences Dialog

In the VIDE Preferences dialog, make the following required settings.
1. Set "Compiler:" by selecting "Borland BCC".
2. Make "Compiler root:" the path to the command-line tools root directory, which is C:\Borland\BCC55 by default.
3. Set the "Debugger:" to 'td32'.
That's it. Choose (Options->Font) or (Options->Editor) to customize VIDE's appearance and editor preferences.

Reference 2Quick Start Guide On Project Configuration, Overview Of Project Configuration and Command-line Tools, Overview Of VIDE Editor On Windows
Visual Windows (BC++) Configuration --- top ---
To minimally configure Visual Windows to work with Borland's Free Command-line Tools, first, run BC++, then click 'Option' from the top menu bar.

Fig. 2: BC++ Option Menu

Click 'BC++ Folders', (Option->BC++ Folders).

Fig. 3: (Option->BC++ Folders)

Under 'BC++ Folders', there are three list items. The bottom two are for automatic location of Command-line Tools installations. The top entry, 'Choose BC++ Folders', is for manual entry of Command-line Tools location. Select 'Choose BC++ Folders' (Option->BC++ Folders->Choose BC++ Folders). An option dialog like the one below in Fig. 4 should appear.

Fig. 4: (Option->BC++ Folders->Choose BC++ Folders) Dialog

Below is a list describing what is in this dialog.
1. Read only entry box containing the system path.
2. Selection list of three components in the command-line tools installation:
  - Executable Directory
  - Include Directory
  - Library Directory
3. Path to the selected component in #2.
4. Selection list of possible values for #3.
Now, complete the following steps to manually provide BC++ with the Command-line Tools folder information.
1. Select 'Executable' from the 'Show Folders at' selection list (control #2)
2. Verify that the 'Folder' entry box (control #3) contains the correct path to the Command-line Tools Bin directory.
3. Select 'Include' from the 'Show Folders at' selection list (control #2)
4. Verify that the 'Folder' entry box (control #3) contains the correct path to the Command-line Tools Include directory.
5. Select 'Library' from the 'Show Folders at' selection list (control #2)
6. Verify that the 'Folder' entry box (control #3) contains the correct path to the Command-line Tools Library directory.
BC++ is now configured to use Borland's C++ Command-line Tools. The editor and it's environment can be further customized, by exploring the other items under the 'Option' menu.

Note:
Additional Library directories and/or Include directories can be specified at the project level, by clicking (Project->Folder Path for Project), and adding entries through the 'Folder Path for Project' entry dialog.

Testing The Installations --- top ---

The following instructions will test to see if the Command-line Tools, the VIDE editor, and the Visual Windows (BC++) environment are installed properly. The Turbo Debugger will be invoked from the command line, and from the two development environments to test it's installation.

Compiler, and Command-line Tools Installation Test --- top ---

To confirm proper installation of the Bcc55 compiler and tools, perform the following three tasks.:

Confirm BCC55 Tools Are In The System Path:
That is... ensure that the .\borland\bcc55\bin and the .\borland\bcc55\include directories are part of the system path, and that the operating system recognizes these two directories.
Compile And Link A Console Program.
Compile And Link A GUI Program.

Confirm BCC55 Tools Are In The System Path --- top ---

Open a dos prompt. Enter the command path, then press [enter]. A string beginning with path= representing the system path should appear. Each path entry is separated by a semi-colon. Verify that borland\bcc55\bin and borland\bcc55\include are in the path string. If these two paths are not found, review the Edit The System Path section of this document.

To confirm that the operating system recognizes the borland\bcc55\bin and the borland\bcc55\include directories as system paths, navigate to the root directory, and make a test working directory, called test_bcc55, as demonstrated below.

Fig. 5: Make test_bcc55 Test Directory

c:\WINDOWS>cd c:\
c:\>mkdir test_bcc55
c:\>cd test_bcc55
c:\test_bcc55>_

In the command line, in the c:\test_bcc55 directory, type the name of one of the executable command-line tools from the list of command-line tools below, and press [enter]. This should generate a list of options for that tool. (Follow MAKE with -? and [enter]. Follow GREP with ? and [enter].)

Free Command-line Tools Package Manifest
BCC32.EXE C++ compiler (32-bit), command-line version

BRC32.EXE Resource compiler (32-bit), command-line version

BRCC32.EXE Resource shell (32-bit)

COFF2OMF.EXE Converts a COFF import library file (InputFile) to the corresponding OMF type import library file (OutputFile).

CPP32.EXE C preprocessor (32-bit), command-line version

FCONVERT.EXE Converts text files between OEM and ANSI formats

GREP.EXE File search utility

ILINK32.EXE Incremental linker (32-bit), command-line version

IMPDEF.EXE Utility used when building apps with Libraries

IMPLIB.EXE Utility used when building apps with Libraries

MAKE.EXE Make utility

RLINK32.DLL Resource linker (32-bit)

TDUMP.EXE File dump utility

TLIB.EXE Utility for maintaining static-link libraries

TOUCH.EXE Change files stamps to current date/time

TRIGRAPH.EXE Converts 3-character trigraph sequences into single characters

**Free Command-line Tools Package Manifest**
BCC32.EXE	C++ compiler (32-bit), command-line version
BRC32.EXE	Resource compiler (32-bit), command-line version
BRCC32.EXE	Resource shell (32-bit)
COFF2OMF.EXE	Converts a COFF import library file (InputFile) to the corresponding OMF type import library file (OutputFile).
CPP32.EXE	C preprocessor (32-bit), command-line version
FCONVERT.EXE	Converts text files between OEM and ANSI formats
GREP.EXE	File search utility
ILINK32.EXE	Incremental linker (32-bit), command-line version
IMPDEF.EXE	Utility used when building apps with Libraries
IMPLIB.EXE	Utility used when building apps with Libraries
MAKE.EXE	Make utility
RLINK32.DLL	Resource linker (32-bit)
TDUMP.EXE	File dump utility
TLIB.EXE	Utility for maintaining static-link libraries
TOUCH.EXE	Change files stamps to current date/time
TRIGRAPH.EXE	Converts 3-character trigraph sequences into single characters

For example, type the name of the compiler (bcc32) at the command line, and press [enter].

Fig. 6: Option List for bcc32

If an options list appears, thats good. It means the operating system is able to find the tool in the Borland\Bcc55\Bin directory. If a list of options appears, but it is not preceded by the Borland/Inprise Copyright (c) notice, it probably means, a tool by the same name was found, somewhere along the system path, before the Borland\Bcc55\Bin directory was searched. If a message saying something like "Bad command or file name" appears, thats bad. It means there is a problem recognizing the Borland\Bcc55\Bin directory through the system path. Carefully review the Edit The System Path instructions and try again.

Compile And Link A Console Program --- top ---
If the path is okay, verify proper command-line tools installation next, by compiling and linking two hello world programs. The first one is a console mode program, the second one, gui mode.

Open up a text editor. Copy the code listed below, and save it as c:\test_bcc55\hello.cpp

#include <iostream>
using namespace std;

int main() {
cout << "Hello!" << endl;
return 0;
}

From the command line, in the c:\test_bcc55> directory, type the following command, and press [enter].

c:\test_bcc55>bcc32 hello.cpp

The following should appear.

Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland
hello.cpp:
Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland

c:\test_bcc55>

This output indicates successful compilation and linking of the hello.cpp program. Type hello at the command line, and press [enter] to run the program. The following should appear.

c:\test_bcc55>hello
Hello!

c:\test_bcc55>

Troubleshooting For Errors Generated By The bcc32 Compiler, Or The ilink32 Linker.
Note: Error messages generated by ilink32 will appear beneath the line that says: Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland.
- If a compile shows a Borland C++ version number that is less than 5.5.1, download and install a current version of the tools. Alternately, the current installation can be upgraded to the current stable version, by downloading, and installing Service Pack 2 and patches from the Borland website.
- If there is an error message saying Bad command or file name or something similar, it is very likely that the PATH is not setup correctly. Review the Edit The System Path section.
- If there is any message beginning with Error..., read it carefully. Which ever tool generated the error, the compiler, or linker, should provided enough information to correct the error. Correct errors in the order they are displayed.
- If the compiler says something like Unable to open include file 'iostream', then there may be a typo in hello.cpp. One or more of the *.cfg files may be in the wrong location, or have incorrect content. Review the Edit The Compiler Configuration File and/or Edit The Linker Configuration File sections. Verify that the case sensitive content of the bcc32.cfg, and ilink32.cfg files is valid, Ensure that bcc32.cfg, and ilink32.cfg are both saved in the .\Borland\bcc55\bin directory, as indicated by the tree diagram below.
  
  Fig. 7: Borland\bcc55\bin Directory Diagram
Compile And Link A GUI Program --- top ---
If everything is okay with hello.cpp, then, in a text editor, save the following code as c:\test_bcc55>hellogui.cpp

#include <windows.h>

#pragma argsused
using namespace std;
WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance,
LPSTR lpCmdLine, int nCmdShow)
{
MessageBox(NULL, "Hello World", "", MB_OK);
return 0;
}

From the c:\test_bcc55> directory, type the following command.

c:\test_bcc55>bcc32 -tW hellogui.cpp

The following should appear.

Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland
hellogui.cpp:
Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland

c:\test_bcc55>

This output indicates successful compilation and linking of the hellogui.cpp program. If hellogui.cpp did not compile and link successfully, see the Troubleshooting section above.

If compilation and linking of hellogui.cpp was successful, run the program by typing hellogui in the command line. A message box should appear.

Click the [OK] button to close the MessageBox. Installation testing for the Command-line tools is finished.

The Main Third Party BCC55 Websites --- top ---

Consult the external sites below for helpful references and tutorials for the command-line tools.

Resource	Notable Content
Dr. Bruce Wampler: BCC32 Quick Reference	Comprehensive list of switches for the ilink32.exe linker and the bcc32.exe compiler. Partial list of the main startup and runtime libraries included with bcc32.exe.
Helmut Pharo: VerifySetup.htm SimpleGUI.htm Make.htm	How to use ilink32 from the command line, and use both compiler and linker options to create small executables. Dynamic linking, Multi-threaded linking, How to include resource files in compilation. Introduction to makefiles.
Pascal Coudert: http://www.webnotes.org/bcc55eng.htm	Helpful introduction to accessing the Windows API functions. Compiling and linking resources (icons, menus, buttons etc...).

Turbo Debugger Installation Test --- top ---

The installation test for the Turbo Debugger, is a simple test to show, that it can be started from any current directory (i.e. TD32.exe, the debugger, is in the system path), and that it can load the specified executable file.

Compile For Debug --- top ---

Before testing, hellogui.cpp must be recompiled, this time with the source debugging option turned on for both the compiler, and the linker. Copy the following command-line string into a blank new document in a text editor.

bcc32 -tW -tWM -v -lv %1

Save the new document as c:\test_bcc55\bcc32_debug.bat The table below explains the argument list.

**Compiler Arguments**
bcc32	Compiler invocation.
-tW	Target is a windows application.
-tWM	Directs compiler to create a multi-threaded .EXE file.
-v	Turn on source debugging for the compiler.
-lv	Turn on source debugging for the linker.
%1	Batch wildcard for the first argument. (used for the name of the source file).

Now compile hellogui by typing the name of the .bat file, followed by the name of the source file, then pressing [enter].

c:\test_bcc55>bcc32_debug hellogui.cpp

Load The Application In The Debugger --- top ---

Assuming the compile for source debugging completed successfully, and an executable for hellogui was created, load hellogui.exe in the debugger by typing the name of the debugger followed by the name of the executable file, as demonstrated below.

c:\test_bcc55>td32 hellogui

After loading hellogui in the debugger, a dos prompt with TD32 in the title bar should appear. It should contain the debugger interface, along with a source listing similar to the screen shot below. If no source code is available to the debugger, assembler will be used instead.

Fig. 8: Turbo Debugger Interface for td32

If the mouse is not working, key [ALT-Enter], to toggle full screen mode (mouse will work in full screen).

Main Window --- top ---
The main td32 debugger window has a pull-down menu bar at the top, and a status bar at the bottom. The status bar at the bottom contains a list of the function keys that are available. Hold down the Alt key. The status bar will show the operations that are available via the Alt+Function Keys. Hold down the Ctrl key, and the status bar will show the operations available via the Ctrl+key combinations. The menu bar at the top contains the File, Edit, View, Run, Breakpoints, Data, Options, Windows, and Help menus. When a menu is expanded and a list item is selected, a sub-window is usually activated that provides information about the selected operation or accepts user input and allows completion of the selected operation.
Sub Windows --- top ---
Within the Main td32 window, a variety of sub-windows can be active at the same time while debugging. Among all active windows, only one of them is the current window, or the top window. Each active window is sequentially numbered (1,2,3, etc.) in it's upper right hand corner. The top window has a small green rectangle at its upper left hand corner, that will close the window when clicked on. Pressing F6, "Next", will sequentially cycle through the active windows, allowing each one of them to be the "top window", in turn.
Debugger Help --- top ---
To learn how to use the Turbo Debugger, click the Help menu at the far right of the td32 menu bar. Click Help on help to get started with basic debugger functionality. Click the Help menu's Index list item, for a pgup/pgdn list of all available help topics.

Also, see Dr. Wampler's objectcentral site for the turbo debugger references listed below.
- Turbo Debugger Help http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-help
- Command Line Switches http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-cmdline
- Keyboard Command Shortcuts http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-keys

VIDE Installation Test --- top ---
The VIDE is a text editor and makefile generator. To test the installation of VIDE, create a test project for the hellogui application.
- Create a New Project --- top ---
  To create the new hellogui project, click on the Project menu button in the top menu bar as shown in Fig. 9.
  
  Fig. 9: VIDE Editor Interface
  
  From the Project menu drop down list, select 'New C++/C Project' (Project->New C++/C Project).
  
  Fig. 10: VIDE Project Menu
  
  A New C++/C Project window, like the one shown in Fig. 11., should appear.
  
  Fig. 11: New C++/C Project Options Dialog
  
  Ensure the following options are selected in the New C++/C Project window.
  - Project Type: C++/C
  - Target name: hellogui.exe
  - Type of build: GUI Application
  - Release/Debug: Debug Version
  - Compiler: Borland BCC32
  Click the [OK] button to accept those options, and create the hellogui project.
  
  After the new project has been created, the C++ Project Editor window appears.
  
  Fig. 12: VIDE C++ Project Editor
  
  With the Project Editor, project properties can be defined or modified. Property information will be compiled into a makefile. The Project Editor can be accessed, independent of the New C/C++ Project process, by selecting 'Edit' under the Project menu (Project->Edit).
  
  To configure properties for the hellogui project, start with the 'names' form, in the Project Editor. Ensure the form contains the information listed below. (Remember: Compiler, and linker flags are case sensitive.)
  - Target File Name: hellogui.exe
  - Makefile Name: Makefile.v
  - Compiler: BCC32
  - Compiler Flags: -q -v
  - Linker: ilink32
  - Linker Flags: -v -Tpe -aa -c
  Here are the flag definitions.
  
  Compiler Flags
  -q Suppresses the compiler ID banner.
  
  -v Turn on source debugging for the compiler.
  
  Linker Flags
  -v Turn on source debugging for the linker.
  
  -Tpe Target a Windows .EXE file
  
  -aa Generate a protected-mode executable that runs using the 32-bit Windows API
  
  -c Case sensitive linking
- Use Project Editor to Add Files --- top ---
  Click the Files tab in the Project Editor. The Files dialog is where source files for the project are specified. VIDE assumes that source files are contained in a single directory. Only add C/C++ files, and resource files. Do not add header files with the Files dialog.
  
  To add source files to the hellogui project, perform the following steps in order.
  1. Click Set Src Dir
  2. Navigate to the c:\test_bcc55 directory.
  3. Leave the file name set to 'Select Directory'. Click Save to close the dialog.
  4. Click the Add button near the bottom of the dialog.
  5. Select hellogui.cpp
  6. Click Open.
  There is only one source file for the hellogui project. Fig. 13 shows how the Files dialog should appear.
  
  Fig. 13: VIDE Project Editor Files Options
- Set Paths --- top ---
  Click the Paths tab in the Project Editor. The Obj. path and Bin path entries are destination directories for any object files, and binary executable files, generated during the make process. Include Paths, and Library Paths, should already contain the same content as the bcc32.cfg compiler, and ilink32.cfg linker, configuration files in the Borland/BCC55/Bin directory.
  
  Fig. 14: VIDE Project Editor Paths Options
  
  For the hellogui project, click the 'Browse' button associated with the Obj. path and Bin path entries. For each entry, navigate to the C:\test_bcc55 directory and click 'Save'. The Include Paths and Library Paths should not need to be modified. If they do, ensure they contain the same information as their corresponding configuration (.cfg) file. Note: $(BCCROOT) == C:\Borland\Bcc55
- Add Libraries --- top ---
  Click the Libraries tab in the project editor. The hellogui project doesn't use any non-standard libraries, so no library files need to be added to this project.
  
  Fig. 15: VIDE Project Editor Libraries Options
  
  The two library files, in the Library Files list, are specified, by VIDE ($(BCC32RTLIB) == cw32), because they are standard libraries for a statically linked, Windows GUI application like hellogui. Most 'real' C++ programs will need additional libfile support to make an executable. Whenever 'undefined symbol' errors appear during compilation, it probably means one or more libraries should be added to the project. In VIDE, the Library Files list is the place to do it.
- Set Defines --- top ---
  If you want to define any constants, and pass them to the compiler, click the Defines tab. Add constant definitions (in the form -Dxxx or -Uxxx) to the Definition Pool list first, and then move them over to the Active Definitions list by clicking the > button. VIDE automatically includes the definitions needed to build Windows 9x, and NT4 executables.
  
  Fig. 16: VIDE Project Editor Defines Options
  
  Reference 3Windows Header File Macros
- The Advanced Tab --- top ---
  Click the Advanced tab. No changes to this form are needed for the hellogui project.
  
  Fig. 17: VIDE Project Editor Advanced Options
  
  The -jp option in the 'debug args:' entry box tells the TD32 debugger to restore the dos prompt when it exits. The rest of the dialog, the 'User Makefile Options' and the 'User Target Options', allow programmers to customize the project Makefile generated by VIDE. Below is a Makefile listing for the hellogui project.
```
#========================================================
#@V@:Note: File automatically generated by VIDE - 2.00/10Apr03! (BCC32).
# Generated 19:29:30 26 Dec 2006
# This file regenerated each time you run VIDE, so save under a
# new name if you hand edit, or it will be overwritten.
#========================================================

# Standard defines:
.AUTODEPEND

# Borland C++ tools
IMPLIB	= $(BCCROOT)\bin\Implib
ILINK32	= $(BCCROOT)\bin\ILink32
TLIB	= $(BCCROOT)\bin\TLib
BRC32	= $(BCCROOT)\bin\Brc32
TASM32	= $(BCROOT)\bin\Tasm32
CC  	= $(BCCROOT)\bin\BCC32

BCCROOT	= C:\Borland\BCC55

HOMEV	=
VPATH	=	$(HOMEV)\include
oDir	=
Bin	=	C:\test_bcc55
libDirs	=	-L$(BCCROOT)\lib;$(BCCROOT)\lib\psdk

incDirs	=	-I$(BCCROOT)\include

LD_FLAGS =	-v -Tpe -aa -c
C_FLAGS	=	-q -v\
	-D_WINVER=0x0400\
	-D_WIN32_WINNT=0x0400

SRCS	=\
	hellogui.cpp

EXOBJS	=\
	$(oDir)\hellogui.obj

ALLOBJS	=	$(EXOBJS)
BCCJUNK	=	*.il* *.csm *.tds
ALLBIN	=	$(Bin)\hellogui.exe
ALLTGT	=	$(Bin)\hellogui.exe

# User defines:

#@# Targets follow ---------------------------------

all:	$(ALLTGT)

objs:	$(ALLOBJS)

cleanobjs:
	rm -f $(ALLOBJS)

cleanbin:
	rm -f $(ALLBIN) $(BCCJUNK)

clean:	cleanobjs cleanbin

cleanall:	cleanobjs cleanbin

#@# User Targets follow ---------------------------------

# BCC32 DEF file: add after = if needed
BCC32DEF =
# BCC32 RT lib: cw32.lib static
BCC32RTLIB = cw32
# BCC32 Startup: c0x32.obj-console, c0w32.obj-winapi
BCC32STARTUP = c0w32.obj

#@# Dependency rules follow -----------------------------

$(Bin)\hellogui.exe : $(EXOBJS)
  $(ILINK32) @&&|
 $(LD_FLAGS) $(libDirs) +
$(BCC32STARTUP) +
$(oDir)\hellogui.obj
$<,$*
import32.lib +
$(BCC32RTLIB).lib
$(BCC32DEF)


|
$(oDir)\hellogui.obj : hellogui.cpp
  $(CC) -c $(C_FLAGS) $(incDirs) -o$@ hellogui.cpp


 
```
  Close the Project Editor by clicking the [OK] button.
  
  The Project Editor can be reached anytime by selecting 'Edit', from beneath the 'Project' menu (Project->Edit). Also, VIDE projects can be re-opened by selecting 'Open' under the 'Project' menu (Project->Open), or by clicking the 'Open Project' icon , then navigating the directory dialog to the desired *.vpj project file.
  
  Reference 4Introduction to Makefiles, How to write a Makefile, Automating Program Compilation - Writing Makefiles
- Build/Compile A Project --- top ---
  The hellogui project is now ready to build. Select 'Make C++/Compile Java' from the beneath the 'Build' menu (Project->Make C++/Compile Java). Build results show in the message window. If there are syntax errors in a source file, right click on the error message and line number. The source file will be opened (if not currently opened) at that line number. Fix any errors, and try build again.
- Execute hellogui --- top ---
  After an error free compile, execute hellogui by clicking the icon, or select the 'Run project' list item underneath the 'Tools' menu (Tools->Run project). A MessageBox with 'hello world' on it should appear. Click [OK] to close the MessageBox. The installation test for VIDE is complete.
- Edit Files --- top ---
  VIDE is also a source viewer and editor. Open project or non-project source files for read only with (File->View). Open a source file for editing with the 'Open File' icon or from the 'File' menu with (File->Edit).
- Activating The Debugger --- top ---
  The Turbo Debugger TD32.EXE, can be launched automatically by clicking the 'Start debugger' button on the VIDE tool bar . When TD32.EXE is launched from within VIDE, mouse is supported, on all windows systems, even when the dos prompt is minimized.
  
  To learn how to use the Turbo Debugger, click the Help menu at the far right of the td32 menu bar. Click Help on help to get started with basic debugger functionality. Click the Help menu's Index list item, for a list of all help topics, using the pgup/pgdn buttons.
  
  Also, see the objectcentral site for turbo debugger references listed below.
  - Turbo Debugger Help http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-help
  - Command Line Switches http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-cmdline
  - Keyboard Command Shortcuts http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-keys
- Learning More About VIDE --- top ---
  To learn more about the general features of the VIDE editor, begin with the Quick Start Guide, and the VIDE C/C++ Tutorial. See the VIDE Borland guide for specific help on using VIDE, with the Borland C++ Compiler 5.5 and Command-line Tools. Below is a list of three useful references that are part of the VIDE documentation.
  - Command Reference http://www.objectcentral.com/vide/help/videdoc/videcmds.htm
  - Editor Reference http://www.objectcentral.com/vide/help/videdoc/videedit.htm
  - Links to the original source of the various documents formerly contained in the VIDE Help System http://www.objectcentral.com/vide/help/vhelp.htm
Visual Windows (BC++) Installation Test --- top ---
To test the installation of Visual Windows, create a test project for the hellogui application in BC++.
- Create a New Project --- top ---
  Start by running the IDE. Click on the 'File' menu button, then select 'New', followed by the 'New Project' menu item (File->New->New Project), as shown in Fig. 18.
  
  Fig. 18: BC++ File Menu Option New Project
  
  The 'New Project' option dialog should appear. Fig. 19 below, shows the dialog initialized with it's default values. Tailor a 'hellogui' project from this by performing the following actions in order.
  1. Change the 'Executable Type' option from 'Console *' to 'Windows'.
  2. Click the [...] button beside the 'Project in Sub folder of' entry box.
  3. Navigate to the C:\test_bcc55 directory, then click [OK].
  4. Type 'hellogui' in the 'Project Name' entry box.
  Fig. 19: BC++ New Project Options Dialog
  
  Click [OK] to close the 'New Project' dialog. You should now see your project directory structure similar to that shown below, in Fig. 20.
  
  Fig. 20: BC++ hellogui Project Directory
  
  Next, insure that the build type is 'DEBUG', and not 'RELEASE', as shown below in Fig. 21.
  
  Fig. 21: BC++ Selecting Project Build Type
- Add Files --- top ---
  Now add the source file, hellogui.cpp, to the project. Begin by highlighting the 'Source files' folder as shown in Fig. 22.
  
  Fig. 22: BC++ Select Project Source Files Directory
  
  With the 'Source files' folder highlighted (making 'Source files' the target directory for the file about to be added.), open the 'Project' menu from the top menu bar, and select 'Add File' (Project->Add File). Or, click the 'Add File' icon.
  
  Fig. 23: BC++ Project Menu Add File Option
  
  Fig. 24: BC++ Add File Icon
  
  A file open dialog should appear. Click the button, or otherwise, navigate to the c:\test_bcc55 directory. Select hellogui.cpp and Click [Open]. Source file hellogui.cpp should now be a child node under the 'Source Files' folder. If so, hellogui.cpp is now a source file in the hellogui project.
  
  Fig. 25: BC++ Source Files Dir. After Adding A File
- Additional Project Configurations --- top ---
  The hellogui project is now ready to build. Most realistic projects (non-trivial ones) will require additional configurations, including ones described below for the BC++ environment.
  - Set Paths --- top ---
    Paths to additional Library and Include directories, can be designated via the 'Folder Path for Project' dialog. Reach it with (Project->Folder Path for Project). Alternately, try (Project->Setting), followed by a click on the 'Link' tab.
  - Add Libraries --- top ---
    The 'Folder Path for Project' dialog also allows specific Object, and Library files to be imported into the project. Navigate with (Project->Folder Path for Project). Click the [>>] button associated with the 'Library/Object File' label. Click [...] and navigate to the needed directory. Select one file at a time, and click [Open] on the file dialog, followed by the [Add] button on the 'Folder Path for Project' dialog. Repeat the sequence to add additional files. Alternately, try (Project->Setting) followed by a click on the 'Link' tab.
  - Set Defines --- top ---
    To define constants select (Project->Setting) from the main menu. A dialog should appear. Click the 'Customization' tab.
    
    Fig. 26: BC++ C/C++ Compiler and Linker Settings Dialog
    
    Enter each constant definition, comma separated, in the entry box located near the 'Macro:' label toward the bottom of the dialog.
    
    Reference 5 Windows Header File Macros
  - Build Modifications --- top ---
    Select (Project->Setting) from the main menu. Each tab in the 'Setting' dialog has a read only display of current compiler options at the bottom. Switch to a different tab, the display gets updated, showing the effect selected options in the dialog have on the compiler arguments. A key to the options can be accessed by clicking the [?] button at the right. Click the 'Details' tab. This form allows direct modification of the compiler options.
- Build/Compile A Project --- top ---
  Now build the hellogui project by clicking the 'Build' menu button, and choosing 'Build' from the sub-menu ('Build'->'Build'). Or just click on the build icon . If the build is successful, the output window should look similar to Fig. 27 below.
  
  Fig. 27: BC++ Build Process Output
- Execute hellogui --- top ---
  Execute hellogui.exe by clicking the 'Build' menu button, and choosing 'Execute' from the sub-menu ('Build'->'Execute'). Or just click on the execute icon. The Hello World dialog box should appear. Click the [OK] button to close the MessageBox.
  
  The installation test for BC++ is now complete.
- Edit Files --- top ---
  BC++ can open project or non-project related source files for editing. Click the 'Open Folder' on the icon bar, or click 'Open' under the 'File' menu (File->Open), then navigate the directory dialog to your source files.
- Activating The Debugger --- top ---
  The Turbo Debugger TD32.EXE, can be launched automatically by clicking the 'debug button' on the BC++ tool bar , or by clicking the 'Debug' menu button, and choosing 'Turbo Debugger' from the sub-menu ('Debug'->'Turbo Debugger'). Mouse is supported, on all windows systems, even with dos prompt minimized.
  
  To learn how to use the Turbo Debugger, click the Help menu at the far right of the td32 menu bar. Click Help on help to get started with basic debugger functionality. Click the Help menu's Index list item, for a list of all help topics, using the pgup/pgdn buttons.
  
  Also, see Dr. Bruce Wampler's objectcentral site for the turbo debugger references listed below.
  - Turbo Debugger Help http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-help
  - Command Line Switches http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-cmdline
  - Keyboard Command Shortcuts http://www.objectcentral.com/vide/help/videdoc/bcc32.html#TD32-keys
- Learning More About Visual Windows --- top ---
  To get familiar with the Visual Windows (BC++) environment, start with the Quick Programming feature. Visit http://phys.cool.ne.jp/physeng/bccstart.htm, or click on 'Quick Programing' under 'To Begin with ...' in the 'Help' system ('Help'->'To Begin with ...'->'Quick Programing').

**Compiler Flags**
-q	Suppresses the compiler ID banner.
-v	Turn on source debugging for the compiler.

**Linker Flags**
-v	Turn on source debugging for the linker.
-Tpe	Target a Windows .EXE file
-aa	Generate a protected-mode executable that runs using the 32-bit Windows API
-c	Case sensitive linking

--- top ---

Document Created January 28, 2007