From: P-Tar Newsgroups: comp.os.msdos.djgpp Subject: Re: about .DXE Date: Tue, 24 Mar 1998 09:44:29 +0100 Organization: Centre d'Etudes de la Navigation Aérienne Lines: 27 Message-ID: <3517726D.59E2B600@cenatls.cena.dgac.fr> References: <3516558C DOT 895BB0D4 AT asim DOT lip6 DOT fr> NNTP-Posting-Host: soffy.cenatls.cena.dgac.fr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk > I have to use the .DXE files some one of my purposes. How to create >a DXE. It's said that there's >a utility simple DXE in then faq. > But there is not enough details about this aspect of djgpp. > If someone know how to use it, it'll be greateful! Yeah, the utility is called dxegen. You can find a basic dxe example in the "tests" distribution of djgpp. Here are a few of the pitfalls I've managed to avoid when playing around with dxe :-) If you intend to load the dxe from within a c++ program you'll have to surround the #include line by : extern "C" { } definitions or you'll get a weird _dxe_load unresolved symbol at link time. If the dxe file contains unresolved symbols, it won't work. BUT I've found a workaround, which is to fully link the file you want to use as a dxe (so you get an exe) and use dxegen to export symbol main. This seems to work, but I guess it's really pushing dxe to its limits. Maybe I'll have to switch to this dlx library which sounds promising. Patrice