Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <4328FD5F.716DF6E9@dessent.net>
Date: Wed, 14 Sep 2005 21:49:35 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Linking with comctl32 lib
References: <20050915043223 DOT 64304 DOT qmail AT web53805 DOT mail 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

Bryan Siever wrote:

> You build a standalong windows app and link in
> (statically) the comctl32.dll into your app. You then

You cannot "statically link a DLL".  The two concepts (static and
dynamic linking) are mutually exclusive.  The only way that you would be
able to statically link against comctl32 was if you had access to the
static version of the library (NOT the DLL + import lib), which as far
as I know, does not come with MS Visual Studio and is not generally
available to anyone outside of MS.  It's certainly not possible with
Cygwin and w32api.

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/