From:	Dave Bird <dave AT xemu DOT demon DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Newby Question
Date:	Tue, 15 Jun 1999 09:07:36 +0100
Organization:	ARS HakeMongers inc...... ><_'> <_"
Message-ID:	<dlQtdyAIngZ3EwNj@xemu.demon.co.uk>
References:	<37655EBE DOT AFFC1A20 AT iocorp DOT com>
NNTP-Posting-Host:	xemu.demon.co.uk
X-NNTP-Posting-Host:	xemu.demon.co.uk:158.152.196.209
X-Trace:	news.demon.co.uk 929451121 nnrp-10:15834 NO-IDENT xemu.demon.co.uk:158.152.196.209
X-Complaints-To:	abuse AT demon DOT net
MIME-Version:	1.0
X-Newsreader:	Turnpike (32) Version 4.01 <dQumtnY$x4rJ2u5tL5fS$n2vuP>
Lines:	26
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <37655EBE DOT AFFC1A20 AT iocorp DOT com>, Walter L. Williams
<walter AT iocorp DOT com> writes
>Good Afternoon
>
>I would like to ask what some might think is a dumb question.
>
>I am going through an O'Reilly book called Practical C Programming.
>I am using the DJGPP compiler with the RhIDE. When I hit the compile
>command on the pull down menu all I get is a ".o" file. When hit run
>from the pull down menu It will get an "EXE" file. Why is it doing this?



 To COMPILE a program i.e. translate it into machine code is not the
 same as to LINK & RUN it (add code of library functions & execute it).

 The first  produces a .O   file for linking;
 The second produces a .EXE file for running. 




-- 
   ^-^-^-@@-^-;-^   http://www.xemu.demon.co.uk/
        (..)__u     news:alt.smoking.mooses

- Raw text -