delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1997/01/17/01:22:27

From: sos AT prospect DOT com DOT ru (Sergey Okhapkin)
Subject: RE: Why is cygwin.dll? -Reply
17 Jan 1997 01:22:27 -0800 :
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <01BC0468.AB4A3B90.cygnus.gnu-win32@gater.krystalbank.msk.ru>
Original-To: "gnu-win32 AT cygnus DOT com" <gnu-win32 AT cygnus DOT com>,
"M DOT Carter AT gcal DOT ac DOT uk"
<M DOT Carter AT gcal DOT ac DOT uk>,
"'Barry Roberts'" <blroberts AT xactware DOT com>
Encoding: 17 TEXT
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Barry Roberts wrote:

>etc. you have running, there is only one copy of the code.  So even
>though each .exe wouldn't grow by 3 MB if they were statically linked,
>they could EASILY take more memory at run-time.  Plus, running cygnus
>utilities from inside bash is faster because the dll is already loaded, it 
just
>has to be mapped into the address space of the new process.

The main advantage of using DLL instead of static linking, is an ability to 
replace DLL with new/patched/improved version without relinking of all 
other stuff.



Sergey Okhapkin
Moscow, Russia

-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019