From: Michael Phelps Newsgroups: comp.os.msdos.djgpp Subject: Re: lib building utility Date: Sat, 28 Sep 1996 23:38:59 -0400 Organization: Computer Science Department, The Johns Hopkins University Lines: 41 Message-ID: References: <01BBAD96 DOT B9F10260 AT slip00-146 DOT btx DOT dtag DOT de> <52kju3$vho AT pulp DOT ucs DOT ualberta DOT ca> NNTP-Posting-Host: hops.cs.jhu.edu Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <52kju3$vho@pulp.ucs.ualberta.ca> To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Try the following: ar ruv libyours.a yourfn1.o yourfn2.o yourfn3.o Then, when you compile your program, simply link with that library: gcc -O2 -Wall yourprog.c -o yourprog.exe -lyours ---Michael Phelps morphine AT cs DOT jhu DOT edu CH3 | N / | ______/ | / \ CH2 _____/ \__|__ // \\ / | \\ // \\______/___CH2 \\ \ / \ / \______/ \_____/ / ------ \ / \ OH \ / OH O Morphine On 29 Sep 1996, B Hodge wrote: > : Anyway, if your source code is not executable, RHIDE will create a = > : library with the option "Compile Menu-Link". Don't forget to specific a = > : name under "Project-main targetname". > > Okay, but obviously there has to be a way of producing a library (.A) file > from the command line somehow. Does anyone know how? > > ----------------------------------------- > Blaine Hodge > Homepage: http://www.ualberta.ca/~bhodge/ > "I am currently between signatures." -me >