Delivered-To: listarch-cygwin AT sourceware DOT cygnus DOT com Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Date: Sat, 13 Feb 1999 19:25:34 +0200 From: Paul Sokolovsky X-Mailer: The Bat! (v1.00 Christmas Preview) UNREG Reply-To: Paul Sokoilovsky Message-ID: <1809.990213@is.lg.ua> To: Mumit Khan , Subject: Re[2]: ld, dlls, and windows libraries References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Mumit, Mumit Khan wrote: [] MK> When DJ's excellent work on ld is released, you'll be able to do: MK> $ gcc -shared -o mydll.dll -mwindows --export-all foo1.o foo2.o Wow! How long to wait for this? MK> The --export-all exports all the non-static symbols as done on most MK> Unix systems. If you want to restrict the exports, you have two choices: And what about implibs? Is there a chance that they will be produced with gcc too, so procedure and data exports will be properly distinguished? That's the thing which causes most pain with gnu-win32 tools now, imho, - suffering an access violation when, due to automatically produced def, which treats all exports as code, some fucnction fetches jump instruction instead of data. MK> Regards, MK> Mumit Best regards, Paul mailto:paul-ml AT is DOT lg DOT ua