Dear Users,
I am tryig to write a program in C (not C++) for a Windows PC. I know the language well, but I am having trouble getting the installation right.
This is Borland C/C++ 5.5. To compile a C program, you activate a DOS window, right? There is a folder into which you type control commands. I call this "Borland." What should this folder contain, beside:
(1) A copy of the compiler, BCC32.exe?
(2) Bit strings which tell the electronics where to find the library. This seems to be fouled up.
(3) Bit strings which tell the electronics where to find the linker. There seem to be two .cfg files involved, but I can't understand what is suppose to go into them.
What is the optimality of buying a C compiler and the documentation in the same shrink wrap, so as to minimuze the likelihood of compatibility isssues?
A related question: Should this work?
---------------------------------------------------------------------
#include <stdio>
{
printf ("Hello, world!\n"
return;
}
-------------------------------------------------------------------------
Especially, one author said to use return 0
The main folder "Borland" contains a .cfg file with:
-I"c:\Borland\Bcc55\include" -L"c:\Borland\Bcc55\lib"
The error message was "Unable to open include file "stdio.h"
TIA
Tom Jones
DrJones@alum.MIT.edu
I am tryig to write a program in C (not C++) for a Windows PC. I know the language well, but I am having trouble getting the installation right.
This is Borland C/C++ 5.5. To compile a C program, you activate a DOS window, right? There is a folder into which you type control commands. I call this "Borland." What should this folder contain, beside:
(1) A copy of the compiler, BCC32.exe?
(2) Bit strings which tell the electronics where to find the library. This seems to be fouled up.
(3) Bit strings which tell the electronics where to find the linker. There seem to be two .cfg files involved, but I can't understand what is suppose to go into them.
What is the optimality of buying a C compiler and the documentation in the same shrink wrap, so as to minimuze the likelihood of compatibility isssues?
A related question: Should this work?
---------------------------------------------------------------------
#include <stdio>
{
printf ("Hello, world!\n"
return;
}
-------------------------------------------------------------------------
Especially, one author said to use return 0
The main folder "Borland" contains a .cfg file with:
-I"c:\Borland\Bcc55\include" -L"c:\Borland\Bcc55\lib"
The error message was "Unable to open include file "stdio.h"
TIA
Tom Jones
DrJones@alum.MIT.edu