From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10211300805.AA22158@clio.rice.edu>
Subject: DXE multiple exports
To: djgpp-workers AT delorie DOT com (DJGPP developers)
Date: Sat, 30 Nov 2002 02:05:19 -0600 (CST)
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

I've got a format defined for the multiple exports.  DXEGEN can now create
the "transfer vector" assembler which can be edited if you don't want all
the globals to be exported.  This is about 60 lines of additional code to
DXEGEN (usually not called).

I've been testing on libiconv to see how it works in a real life example.
It finds two global symbols which really shouldn't be visable ... so
I edit them out of the configuration.

Haven't messed with C++ stuff (not needed in iconv).

Next up on the list is the DXE2LIB executable, which will examine an
existing DXE and create a transparent set of call wrappers to load the
DXE (with all imports) and jump to the appropriate place.

The question of the moment is: where should the default directory for
DXEs be in DJGPP?  The only one we currently have is EMU387, and it lives
in $DJDIR/bin ...
$DJDIR/bin AND $DJDIR/lib seem like decent defaults.  Path?