From: Andy Eskilsson <x-aes AT telelogic DOT se>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Simple Query on multiple sources
Date: 21 Apr 1997 16:28:43 +0200
Organization: Telelogic AB, Sweden
Lines: 27
Sender: x-aes AT vega
Message-ID: <ksohb8jvqc.fsf@telelogic.se>
References: <861628816 DOT 14833 DOT 0 AT itsb DOT demon DOT co DOT uk>
Reply-To: x-aes AT telelogic DOT se
NNTP-Posting-Host: vega.telelogic.se
Mime-Version: 1.0 (generated by tm-edit 7.101)
Content-Type: text/plain; charset=US-ASCII
CC: cs19 AT cityscape DOT co DOT uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

/ cs19 AT cityscape DOT co DOT uk (BDC Client Team) wrote:
| Can anyone help me with mulitple sources? 
| 
| I understand about compiling different sources to .o files and then
| linking the .o's to a .exe, but I am unsure about #includes. 
| 

Simply, the world isn't only .c and .o's.. 

We have also .h's (h for header) that contains descriptions of the
stuff in the associated file (.o or .a).. these descriptions
(definitions) is needed by the compiler so he knows what stuff lies in
the files you will link together to an .exe-file.

And then there also is .a-files, libraries (a as in archive(?)) which
is basically a bunch of .o-files, for example libAllegro.a, and used
through something like -lAllegro at linking stage. 

Shortly include-files contains definitions of functions/variables that
the compiler needs (the definitions) at compile-time. These
functions/variables is then later on put into the .exe file at linking
time.

Uhm.. Well hopefully I can shred some light, a hint is to get a good
book about c/c++ and get more info from there.

	/Andy