dev-cpp-users

[Dev-C++] newbie question on header files

[John K. <jki...@po...>]

How do I compile on the command line using gcc, g++, or another 
compiler , circumventing Dev-C++ (which I relly like))?.
Specifically, I receive errors b/c of my #include statements 
(<iostream> and <string>), which I understand to be 
somehow "standard". When I use <stdio.h>, my code compiles fine. 

I will be moving to unix where I will only have gcc and other unix 
tools, and I am trying to get oriented to that environment.

Re: [Dev-C++] newbie question on header files

[jansb000 <jan...@wx...>]

On UNIX (LINUX) you may enjoy X-Windows, also a graphical user interface.
For GCC i believe there is RHIDE for UNIX. This may be what you are looking
for.
I have RHIDE for DOS, which is really good. I have heard that there is a
version for UNIX too (it's open source).

I can also recommend the newsgroup comp.os.msdos.djgpp; they discuss RHIDE
(among others) and they can point you to other resources I am sure.

----- Original Message -----
From: "John Kilbourne" <jki...@po...>
To: <dev...@li...>
Sent: Thursday, December 20, 2001 9:21 PM
Subject: [Dev-C++] newbie question on header files


> How do I compile on the command line using gcc, g++, or another
> compiler , circumventing Dev-C++ (which I relly like))?.
> Specifically, I receive errors b/c of my #include statements
> (<iostream> and <string>), which I understand to be
> somehow "standard". When I use <stdio.h>, my code compiles fine.
>
> I will be moving to unix where I will only have gcc and other unix
> tools, and I am trying to get oriented to that environment.
>
>
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users

Re: [Dev-C++] newbie question on header files

[Jason H. <jas...@bt...>]

The current C++ standard says that the standard libraries don't have the .h
at the end, but allows the .h though (depreciated I think).

So #include <iostream.h> and #include <iostream> are equivalent, although
some implementations have a difference in the use of namespaces. One thing
of note however is the C standard libraries, <stdlib.h>, <stdio.h>,
<string.h>, etc...are all libraries that came with C, but using the C++
notation they change too <cstdlib>, <cstdio>, <cstring>, etc... they all
have a 'c' in front of them, but notice the <cstring>, in C++ there is a
<string> library which is different as it defines the std::string container
intruduced with C++, whereas <cstring> has the functions strcpy(), strstr(),
strcmp(), etc...

I don't know much about using gcc from the command line, but there are
pleanty of tutorials on the web. Checkout the man pages with linux.

Hope this helps, Jason.

----- Original Message -----
From: "John Kilbourne" <jki...@po...>
To: <dev...@li...>
Sent: Thursday, December 20, 2001 8:21 PM
Subject: [Dev-C++] newbie question on header files


> How do I compile on the command line using gcc, g++, or another
> compiler , circumventing Dev-C++ (which I relly like))?.
> Specifically, I receive errors b/c of my #include statements
> (<iostream> and <string>), which I understand to be
> somehow "standard". When I use <stdio.h>, my code compiles fine.
>
> I will be moving to unix where I will only have gcc and other unix
> tools, and I am trying to get oriented to that environment.
>
>
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users

Re: [Dev-C++] newbie question on header files

[Luigi S. <gi...@li...>]

Hi,

I think that the errors you get are related to the fact that "g++" is 
unable to locate the C++ standard include files on your system, you should 
explicitly tell the place using the "-I" option.

If you plan to use "gcc" from the command line I suggest you look for some 
file describing the options. As Mr. Hardman says, there are many places 
where you can find such files, try the home page of Dev-C++, there should 
be some link, or try http://www.delorie.com/gnu/docs

In my opinion, before moving to Unix, be sure you know how to use an editor 
and  also read something about "make" and "gdb".

As for other compilers, a good one (I mean pretty much ANSI compliant, but 
it works on Windows/Dos only) is the Borland one, you get it by downloading 
the Borland free command line tools package (see http://www.borland.com, 
and from there work your way to the right page). The package comes with the 
file bcb5tool.hlp that explains how to use the tools.

I myself use gcc (or bcc), most of the times, from the command line; to 
save me some typing I have developed two small, very simple programs (one 
for compiling a single file, the other for generating simple makefiles), 
they are available (as sources) at www.geocities.com/gisan1 follow the link 
clt_gnu. The programs use ANSI C(89), and it is not hard to modify them so 
that they can be ported to Unix (I will be writing a Linux port of them 
shortly after Christmas).If you need some help (or if you want the binary 
form of the programs), let me know: I'm a newbie myself, but I'll do what I 
can.

I hope the above is of some help.

At 15.21 20/12/01 -0500, John Kilbourne wrote:
>How do I compile on the command line using gcc, g++, or another
>compiler , circumventing Dev-C++ (which I relly like))?.
>Specifically, I receive errors b/c of my #include statements
>(<iostream> and <string>), which I understand to be
>somehow "standard". When I use <stdio.h>, my code compiles fine.
>
>I will be moving to unix where I will only have gcc and other unix
>tools, and I am trying to get oriented to that environment.
>
>
>_______________________________________________
>Dev-cpp-users mailing list
>Dev...@li...
>https://lists.sourceforge.net/lists/listinfo/dev-cpp-users

--
gisan
gi...@li...