Patrick, check out:

http://community.borland.com/article/0,1410,20997,0.html

and try to find the next article in the series that describes make/makefiles

I also tried to find a nice article at redhat that had a good basic intro to make/makefiles but it seems too have disappeared. The basic idea is that rather than issuing each separate command to the compiler whether it is bcc or gcc, you write a text file that scripts the calls. For small projects it is not really necessary, but if you have two or more source code files it starts to come in handy. I'm not really familiar with the Bourland bcc for windows, but it must function in a similar fashion to the gcc compiler on linux. I notice Bourland includes a make.exe file in their distribution, so just evoke it by typing 'make' while you are in the same directory as the makefile you create if you decide it is necessary. In essence, a makefile functions like the project or *.cpp files of something like the Microsoft C++ Intergrated Development Environment/compiler.

The best simple example I can give is to look at the stuff at NIST ftp by Judah Levine, and in particular the unix Nistime files:

ftp://time-b.nist.gov/pub/daytime/

"1. If you have a workstation with "standard" UNIX that supports tcp/ip communication over the internet, then you can build a version for your machine using files sw.c, tcp_time_client.c and Makefile. "

I couldn't get Judah's makefile to play for me on RedHat 6.2, so I rewrote it as per the attached file, which you should open in Notepad and examine.

best of luck, and thanks for turning me on to Bourland's free bcc compiler. I have used MS C++ on windows, but most of my compiling these days is on Linux using GNU gcc.

Also, do a web search for 'makefiles'

clay