Re: creating stand-alone extended tclsh
- From: Alexandre Ferrieux <alexandre.ferrieux@xxxxxxxxx>
- Date: 29 Apr 2007 05:03:46 -0700
On Apr 29, 12:06 pm, David Gravereaux <davyg...@xxxxxxxxx> wrote:
4) relish your in your large executable, though I prefer those grilled red onions
and mustard to top my dogs.
I'm a bit surprised by this aversion of static linking. Though
obviously it's a waste of system resources for libc or libX11, for
most of the rest of libs, it changes absolutely nothing because the
executable is the only one in the system that will *ever* use it
(specific libraries : only for specific needs). While static linking
has several pointwise advantages I have come across:
- debugging in old versions of gdb
- no risk of half-install
- no risk of version mismatch
- single-file installerless executable (like a *kit but with no
startup overhead due to extracting DLLs to temporary files).
-Alex
.
- Follow-Ups:
- Re: creating stand-alone extended tclsh
- From: Gerald W. Lester
- Re: creating stand-alone extended tclsh
- References:
- creating stand-alone extended tclsh
- From: Will Parsons
- Re: creating stand-alone extended tclsh
- From: David Gravereaux
- creating stand-alone extended tclsh
- Prev by Date: Re: integer value too large?
- Next by Date: Re: creating stand-alone extended tclsh
- Previous by thread: Re: creating stand-alone extended tclsh
- Next by thread: Re: creating stand-alone extended tclsh
- Index(es):