X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=FSJgZOlP9wJQEst7bD14HMWaIGU7XB/VdDW8vbSFy6C XdsYn9HuVJvGijPCeL5uBszK4mCA1W1E2sozT841ltPb8LNvzBM7NnrrP9r03Tv2 r0/3os4j3uWOrbLrd8sLYBe2H7hkBkeqrfNBTd2vDPydgYbYZGHKI9ZEPOrtwiCc = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=Vj1ew05Aj8ETxhizCjq5T+6dn2g=; b=bqPu+6Lm5B8uo6wnx Z3tRQkYjJ7NChr5qzB0Oeo6Xqo/SB7VZslcJLnbRgZYHTaj0mCS+rx/pCWRH6UgR 281WuaV/EuWPejOPQz4GWHRElHQQ4d1oXd3f50SjyrVEHb1SQJUciOcKXOlFDn3Y K9keZIi85kBJAeI9+O/i3JNi4c= 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_50,RDNS_NONE autolearn=no version=3.3.2 X-HELO: etr-usa.com Message-ID: <527AF109.4080500@etr-usa.com> Date: Wed, 06 Nov 2013 18:46:49 -0700 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Cygwin-L Subject: Re: Find dll name corresponding to an import library References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 11/6/2013 15:31, Jean-Pierre Flori wrote: > > Is there a canonical way to do so? The canonical way is to name your import libraries so that the name of the corresponding DLL is obvious. Non-Cygwin import libraries are traditionally named after the DLL: foo.lib is for foo.dll. Cygwin's stock build system is a bit different, due to POSIX naming norms, but the transform is simple: libfoo.a is for cygfoo.dll. If you have an import library with a name that doesn't conform to one of these schemes, you might be able to dig the DLL name out of the library file. Through some futzing around, I've discovered that this works: $ objdump -s foo.a | grep cyg.*dll$ That assumes that the DLL uses the "cyg" prefix. Just grepping for "dll$" would be a better option if you weren't sure about even that. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple