Message-Id: <200509150444.j8F4iEit012403@delorie.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Gary R. Van Sickle" To: Subject: RE: Linking with comctl32 lib Date: Wed, 14 Sep 2005 23:43:35 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20050915043223.64304.qmail@web53805.mail.yahoo.com> X-IsSubscribed: yes > From: Bryan Siever > Sent: Wednesday, September 14, 2005 11:32 PM > To: cygwin AT cygwin DOT com > Subject: Linking with comctl32 lib > > Greetings, > This question came up after a lively discussion with several > other developers. Let me clarify my question. > You build a standalong windows app and link in > (statically) the comctl32.dll into your app. By definition that is impossible. The "D" in DLL stands for "Dynamic". > You then want to > deploy your application, your application now contains parts > of the dll but not all of them due to static linking. No, it doesn't. The .lib you linked to is a stub. It doesn't contain any part of the DLL code, regardless of how much of the library you use. IIUC, the .lib under discussion isn't even of Microsoft origin; it's generated by a Cygwin or Mingw program. -- Gary R. Van Sickle -- 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/