From: Nebuchadnezzar <Nebuchadn AT NOSPAMquayles1 DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Newby Question
Date: Tue, 15 Jun 1999 16:42:25 +0100
Message-ID: <rK0vZcAhRnZ3Ew4o@quayles1.demon.co.uk>
References: <37655EBE DOT AFFC1A20 AT iocorp DOT com> <929403957 DOT 546 DOT 59 AT news DOT remarQ DOT com>
NNTP-Posting-Host: quayles1.demon.co.uk
X-NNTP-Posting-Host: quayles1.demon.co.uk:193.237.131.218
X-Trace: news.demon.co.uk 929468370 nnrp-01:29877 NO-IDENT quayles1.demon.co.uk:193.237.131.218
X-Complaints-To: abuse AT demon DOT net
MIME-Version: 1.0
X-Newsreader: Turnpike (32) Trial Version 3.05 <X57Tfjb234BpiTjNHTJmyPlHTE>
Lines: 24
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

In article <929403957 DOT 546 DOT 59 AT news DOT remarQ DOT com>, Al Morgan
<muaddib AT proaxis DOT com> writes
>The reason you don't get a .EXE file when you compile it this:
>when you compile the program, it first compiles it to a .O file, then
>/links/ the .o file to make an .EXE.
>So you want to "Make" instead of "Compile", making will compiler, link, and
>all that stuff, leaving you with a .EXE.
>
>This is used for... well, I'm not sure exactly how object files are used,
>but I know when you make large programs using makefiles, you get a bunch of
>them.
>
>
The .o file is the object code, when using a large multifile project it
is useful to compile to these separately and then to link them all, that
way if you get linker errors you only have to re-compile the suspect
file, not the lot. If you copile straight to an exe you have to do the
lot again.
--____    ___   _   _  _____  ____
 | __ \  / _ \ | | | ||_   _|| __ \   E-mail: nebuchadn AT quayles1 DOT demon DOT co DOT uk
 ||  \ || [_] || |_| |  | |  ||  \ |     ICQ: 13313977
 ||__/ || | | | \   /  _| |_ ||__/ | Website: <NOT UP YET!>
 |____/ |_| |_|  \_/  |_____||____/    Phone: 1100000101010110101001100011111
                 C Programmer, Beer drinker. Life Sucks!