X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <48F8C28C.303A07CE@dessent.net> Date: Fri, 17 Oct 2008 09:51:24 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygwin:g++linker problems References: <363024 DOT 77609 DOT qm AT web55805 DOT mail DOT re3 DOT yahoo DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com jayshankar nair wrote: > The libraries is build with gcc(in cygwin environment). Something to do with flags or packages. Shared libraries have the extension .dll on Windows, not .so. Specifying -lf will find your library if you named it cygf.dll or libf.dll, or if you created an import library libf.dll.a. (It will find other variants as well, like f.lib. Read the linker manual for the full list.) If you want to name a DLL with a nonstandard extension like .so there is nothing stopping you, but you can't expect the -l switch to find it if you do. You can specify it to the linker by filename directly though. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/