C++Builder compiler

[reynolds]

I've downloaded just the compiler for C++Builder, but I am stuck on how to link in the header files. The docs say:

2. From the bin directory of your installation:
a. Add "c:\ Borland\Bcc55"
to the existing path
b. Create a bcc32.cfg file which will set
the compiler options for the Include
and Lib paths (-I and -L switches to
compiler) by adding these lines:
-I"c:\ Borland\Bcc55\include"
-L"c:\ Borland\Bcc55\lib"
c. Create an ilink32.cfg file which will set
the linker option for the Lib path by
adding this line:
-L"c:\ Borland\Bcc55\lib"

I am getting the error message:
Error E2209 prog.c 2: Unable to open include file 'stdio.h'

And I think it's because of configs that haven't been implemented properly.

What exactly do you have to do on b) and c) ?

AtW? Mark? Anyone else?

[MilanBenesXP]

that one is easy to solve.

Just chuck out c++ and go

to microsoft's site and download .Net

Milan.

[ScotsPine]

reynolds:

idle interest..are you a contractor?

[AtW]

C++Builder

i presume you talking about Borland's free Borland C++ compiler - the C++Builder is visual environment that uses compiler as backend.

check your #include statement, are you using #include <stdio.h> or #include "stdio.h" post here file source if it still fails as well as output from SET command in cmd.
alternatively you can set INCLUDE environmental var to point to your main include files dir

they are different in terms of where they'd look for include files. cant bloody mind which one each - just try the other one, also check path to INCLUDEs.

Milan is right tho - C++ does not cut it anymore (same as Borland), get up to speed with C#.

[Mark Snowdon]

re: bcc

Reynolds

the cfg file is there just to save you having to put loads of options on the command line.

-I <path> gives the path to the include files - so your example assumes that you have installed into the c:\ borland directory, if you have put it elsewhere then change this line as appropriate

if in your code you have #include <stdio.h> then it will look in the include path, if you have "stdio.h" it looks in the current directory - ie where the source code is. for standard includes you should always be using < >

the PATH (where dos looks for executables) is I guess OK since it is finding the compiler.

borland used to create a script to set up the environment PATH, INCLUDE etc for you - cannot remember what they called it - bcc32.bat or something?

I take it that you are just starting out with C++ ?

what is your main language ? are you a VB (spit) man?


I used to recommend either the Dietel&Dietel [how to program c++ - includes ms vc++] or Bruce Eikkle[thinking in c++] (have to check those name spellings) books - have a look at them in a bookshop to see if you get on with the style. (the Bruce Eikkle is free on the web if I remember correctly - mindspring.com I think ?)

Many people find Stroustrop etc heavy going although I always also recommend K&R as an excellent example of a language definition.

Couldnt comment on C# although I understand the momo people are porting to Linux.

Java is probably easier to use for getting to grips with OO - plus the software is free and there are lots of examples floating about.

[AtW]

Re: re: bcc

> I always also recommend K&R as an excellent example of
> a language definition

worth noting that good old Kernigan and Richie (sp?) describe C, not C++. Basic concepts should be helpful to understand C++ tho.

[SupremeSpod]

Re: re: bcc

A little pointer,

error 2 - File not found
error 5 - Access Denied

Spod - In "In the beginning" mode!

[reynolds]

bcc

cheers fellas. ive got the solution for anyone who wants the tool on their system:
community.borland.com/art...05,00.html