delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/07/06/16:51:15

From: sparhawk AT eunet DOT at (Gerhard Gruber)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Making Libraries
Date: Mon, 06 Jul 1998 20:36:12 GMT
Organization: Customer of EUnet Austria
Lines: 29
Message-ID: <35a41e42.1532116@news.Austria.EU.net>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980706110653 DOT 26454D-100000 AT is>
NNTP-Posting-Host: e188.dynamic.vienna.at.eu.net
Mime-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Destination: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
From: Gruber Gerhard
Group: comp.os.msdos.djgpp
Date: Mon, 6 Jul 1998 11:23:22 +0300 (IDT):

>This is only true if you have enough memory to leave all of the shared
>library in the cache.  Please keep in mind that shared libraries are
>typically used on a multi-processing system, where several programs running
>simultanously, including the OS itself, share the same library copy.  This
>paradigm is useless with DJGPP, even if it runs on Windows (since

I think this is the major problem because DJGPP is DOS based. So the advantage
for using shared libraries are less than on Windows or Unix. But I think that
even compiling the code that manages long filenames and other stuff that is in
every djgpp Programm may reduce the size of the executables drastically. I
already thought about a method of using shared objects that I can link in at
runtime but I don't know if I have the time to do it and it would be clumsy to
use because there is no support from the linker. I would have to write an
additional linker to support this kind of objects. On the other hand, if this
would appeal to more people than this could be included in the linker
distributed with DJGPP.
--
Bye,
   Gerhard

email: sparhawk AT eunet DOT at
       g DOT gruber AT sis DOT co DOT at

Spelling corrections are appreciated.

- Raw text -


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