From:	George Foot <mert0407 AT sable DOT ox DOT ac DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Total Newbie
Date:	10 Nov 1997 09:32:09 GMT
Organization:	Oxford University, England
Lines:	39
Message-ID:	<646kap$bgt$2@news.ox.ac.uk>
References:	<6468qq$igl$1 AT nnrp1 DOT rcsntx DOT swbell DOT net>
NNTP-Posting-Host:	sable.ox.ac.uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On Mon, 10 Nov 1997 00:17:35 -0600 in comp.os.msdos.djgpp Robert Denby <Denby AT Swbell DOT net> wrote:
: I have  just recently downloaded DJGPP and was unable to get some of the
: samples to compile. I didn't have much luck after reading the FAQ's either.
: I am a Visual Basic Programmer and am totally new to C.   Also, I was trying
: to use the RHIDE program.

: I've gotten hold of some tutorials to work with.  However, I still need to
: learn to use the compiler to build the example programs.

What example programs?

The basic compilation and linking instructions are at the end of
readme.1st, which you should have; if you don't have it, get it from
the v2 directory on simtelnet mirrors, e.g.:

ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2/readme.1st

Briefly, if your source code is `hello.c', to compile it you use:

gcc -c hello.c

This will create a file `hello.o'. To link one or more .o files into
an executable `hello.exe' you use:

gcc -o hello.exe file1.o file2.o file3.o ....

Other options are discussed in readme.1st.  Note particularly that if
you're using C++ you need to use `gxx' instead of `gcc' to do the
linking.  For the compiling you should still use `gcc'.

If you are using RHIDE, things are different but should be explained
in its documentation.  It's best to try things out and ask about
specific problems (giving information about what you were doing and
what the compiler or RHIDE said was wrong).

-- 
Regards,

george DOT foot AT merton DOT oxford DOT ac DOT uk

- Raw text -