|RudeServer™ Professional C++ CGI Development Libraries|
Installing, configuring and testing the tools takes 5 steps (each of these links goes to the appropriate section on this page).
Notes/Corrections: The links in this How-To were last verified on December 8, 2006. If the links are not valid, or you have corrections or advice for improvements, please contact me.
NOTE: Before you can download the tools, you will have to create an account with Borland® (or log into an existing account). After accepting the license agreement, you will have the option of downloading the file using FTP or HTTP. If you use HTTP, Borland will make you download a downloader to actually get the file. I would recommend using FTP if the option is available.
Run the setup program. Just click the file (freecommandLinetools.exe) downloaded in step 1 and accept all the defaults.
( More explicitly, choose: Next, then Finish, then Yes )
By default, it should install everything to C:\Borland\BCC55 (The rest of this How-To assumes this location).
FYI: For the uninitiated, you should know that bcc32.exe is the main program used from the command line to compile and build programs. Lots of other files are installed: the standard C and C++ header files, object libraries containing the standard library routines, some help files, lots of example programs that most of us will never even peruse, and a few helper programs like the linker (ilink32.exe) and the library manager (tlib.exe) and some oldies but goodies like grep, make and touch.
Which would you rather type to invoke the tools?
After the setup program is run (step 2), a whole bunch of executable programs are placed in a new directory : C:\Borland\BCC55\Bin. This step makes it possible for the Operating System (Windows) to find these new executables by name. If you don't do this, then you will need to specify the full path to bcc32 everytime you use it.
To do this on Windows 98
Add the path to the C:\Autoexec.bat file.
To do this on Windows NT
Windows NT is very similar to Windows XP. See Christopher Moeller's Supplementary Information page if you need step by step instructions.
To do this on Windows XP
Bring up the Environmental Variables dialog (figures 3-1 and 3-2):
Append ";C:\Borland\BCC44\bin" to the PATH variable (figure 3-2)
WARNING: If other paths are already present - don't remove them. Each path listed is separated from others by a semi-colon. Each path is the location of executables that are not in the standard locations and if you remove them some other applications in your system may break
|Set up some configuration files|
If you are having problems with this step, it can also be performed from the command line:
Optionally Create ilink32.cfg:
|Test the Installation|
If you can perform the following tests, then you know that your environment is set-up correctly. That way, when your program won't compile a week from now, you know that the installation is not the issue.
Open a command prompt:
FYI: IF you are going to be using Borland's Command Line tools, you need to be able to open a command shell in your sleep. Luckily, it is only 2 steps and comes standard on all Windows Versions.
1. Start->Run... (figure 5-1)
Hit OK - the Black Box that appears is the Command Prompt or Command Line
Now you should be able to run bcc32 from the command prompt:
3. Let's create a "Hello World" application to test everything....
From the command line, make a folder on your Desktop called mytest
and move into it (figure 5-4)
test.cpp (figure 5-5)
A strange world will open up to you, into which you should type this code (see figure 3-7):
To Exit this strange blue world, USE YOUR MOUSE to go to the file menu - save first! then exit!
Once you are at the command line again, compile and link you application using bcc32:
The results should look like this:
If they did, then YAY! You are done. Happy Coding.
You can run the program you just created by typing the name of it: test
FYI: If you examine the directory where you just built your test program, you will see 4 files. test.obj and test.tds are intermediary files, and can be deleted. IF you click on test.exe, a black window will pop up and disappear right away. The window automatically closes when the application exits and is normal. Usually, you will want to open up a command prompt and run your programs from within instead of clicking on them.
"Borland" and "C++Builder" are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. This How-To is independent of Borland Software Corporation and has not been authorized, sponsored, or otherwise approved by Borland Software Corporation.
Copyright ©2006-2007 RudeServer™