coapp-developers team mailing list archive
-
coapp-developers team
-
Mailing list archive
-
Message #00738
Re: use of static libs permitted?
-
To:
coapp-developers@xxxxxxxxxxxxxxxxxxx
-
From:
"William A. Rowe Jr." <wmrowe@xxxxxxxxx>
-
Date:
Fri, 01 Oct 2010 14:50:24 -0500
-
In-reply-to:
<AANLkTi=QaS-5Vvw5skd7Eiy9PkfpE6dQJ08kdC7rOXQF@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
On 10/1/2010 7:46 AM, Olaf van der Spek wrote:
> On Fri, Oct 1, 2010 at 2:38 PM, Philip Allison
> <mangobrain@xxxxxxxxxxxxxx> wrote:
>> There is a use case for creating a minimal, stand-alone version of a
>> particular package, bundling just what it needs into a deployable
>> image, but I can't remember what conclusions have been reached about
>> that.
>
> Sometimes a single exe is desirable. In that cases, static linking is
> the only option.
If I were building the zip/zlib packages, I wouldn't have an issue with the
zip and unzip utilities depending on zlib.dll, that is as it should be.
I would have an issue if we couldn't compile the standalone unzipsfx stub
binary without linking to zlib.lib. That is an example where dlls vs libs
becomes significant.
References