Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Dave Korn" To: Subject: RE: why is -L/usr/local/lib necessary? Date: Tue, 14 Dec 2004 17:36:01 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-OriginalArrivalTime: 14 Dec 2004 17:36:01.0203 (UTC) FILETIME=[60EB5030:01C4E203] > -----Original Message----- > From: cygwin-owner On Behalf Of Dave Korn > Sent: 14 December 2004 17:28 > 2) You can't statically link against a .dll anyway. You > statically link (at > compile time) against .a files; you dynamically link (at > runtime) against .dll files. Minor correction: you can in fact link against a dll, but it doesn't actually link the function from the dll into your exe, it links a __imp__FunctioName stub. So it's the same as linking against the corresponding static import library (libfoo.dll.a in this case) anyway. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/