www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/03/29/19:26:45

Xref: news2.mv.net comp.os.msdos.djgpp:2251
From: malcolm AT manawatu DOT gen DOT nz (Malcolm Taylor)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Where functions belong...
Date: Fri, 29 Mar 1996 06:10:14 GMT
Organization: Grafik Software
Lines: 19
Message-ID: <4jfup1$apl@news.manawatu.gen.nz>
References: <199603262007 DOT MAA10437 AT sirius DOT cs DOT pdx DOT edu>
Reply-To: malcolm AT manawatu DOT gen DOT nz
NNTP-Posting-Host: malcolm.manawatu.gen.nz
Mime-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

idr AT cs DOT pdx DOT edu (Ian D Romanick) wrote:

>I have a suggestion for the next release of DJGPP.  I think there's
>quite a few functions that should be moved out of libc.a.  These
>functions include all of the DPMI stubs and the dosmemget() types.  The
>reason for this is that many people will probably want to use these
>functions in DXEs, but you can't link libc.a into a DXE.  Or am I just
>missing something?

Many of the functions in libc.a need global variables to be present to
work (most notably all the printf etc type functions need the stdio
file), and this is the reason that they cannot be linked into a DXE.
The functions within the DXE know nothing about functions or variables
within the main image. As long as you take note of this and don't link
in any functions from libc.a (ie don't use them) into your DXE then
you should be fine.

Malcolm

- Raw text -


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