Date: Sun, 3 Nov 1996 18:34:59 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: HiGhLaNDeR <highlander AT redestb DOT es>
Cc: djgpp AT delorie DOT com
Subject: Re: non-standard name libs
In-Reply-To: <327bacb4.30207215@news.redestb.es>
Message-Id: <Pine.SUN.3.91.961103182333.28604E-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Sun, 3 Nov 1996, HiGhLaNDeR wrote:

> 	I was reading the docs until i couldn't do it more and i
> didn't found how to build a library. I saw something like the "ar"
> program but i'm not sure.

That's it.  To read the ar docs, type this from the DOS prompt:

	info binutils ar

> 	Also it's very important for me to have one library with a non
> standard "lib----.a" name, for example i want to link a library called
> "mylib.lib". How i can do this from rhide and from the command line?

I don't use RHIDE, but from the command line you should say this:

	ar cq mylib.lib file1.o file2.o file3.o ...

Btw: why is it important to call this .lib rather than .a?  I think this 
might get you in trouble in some cases.  Many GNU tools know about the .a 
extension, but not about the .lib one.  One example that comes to mind is 
the GNU Make.