From:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: compiling libraries...
Date:	9 Mar 1997 05:20:08 GMT
Organization:	The National Capital FreeNet
Message-ID:	<5ftha8$if7@freenet-news.carleton.ca>
References:	<331DBAB2 DOT F7F AT comports DOT com> <331E016F DOT 5E7A AT cam DOT org>
Reply-To:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host:	freenet2.carleton.ca
Lines:	20
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Easiest way: get RHIDE.

Then, make your library like this: make a new project. Change the
targetname from ending in .exe to ending in .a. Then, put all the routines
that every part of the library will need in one .c file, write the rest in
a modular fashion in other .c files. Compile and link, and debug, and
debug, and debug...

.a files are Archives made by "ar". They have a bunch of .o files, which
are linked in only as needed by ld. You will probably want your library to
have a name like libxxxxx.a; then you can put it in %DJDIR%/lib and link
it with the gcc command -lxxxxx.

--
    .*.  Where feelings are concerned, answers are rarely simple [GeneDeWeese]
 -()  <  When I go to the theater, I always go straight to the "bag and mix"
    `*'  bulk candy section...because variety is the spice of life... [me]
Paul Derbyshire ao950 AT freenet DOT carleton DOT ca, http://chat.carleton.ca/~pderbysh

- Raw text -