From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20210 invoked from network); 2 Jun 2000 13:44:47 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 Jun 2000 13:44:47 -0000 Received: (qmail 8351 invoked by alias); 2 Jun 2000 13:44:34 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11725 Received: (qmail 8344 invoked from network); 2 Jun 2000 13:44:34 -0000 Date: Fri, 02 Jun 2000 14:43:31 +0100 From: Peter Stephenson Subject: Re: Getting dynamic loading to work on cygwin In-reply-to: "Your message of Fri, 02 Jun 2000 12:03:05 BST." <0FVI00DP2XD5AS@la-la.cambridgesiliconradio.com> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Message-id: <0FVJ00H7A4SJ18@la-la.cambridgesiliconradio.com> Content-transfer-encoding: 7BIT > The > changes to what we have already should be fairly mechanical but will still > require a bit of work. Hmm, looks like I spoke too soon. I don't see a way of exporting symbols from the main executables which DLL's will recognize. However, the old system V trick of making the main body of the code a DLL and zsh.exe a boot-loader ought to work, and isn't that difficult (again, the hard part is really just fiddling the scripts etc.). Another thing I missed before was that the lib*.a libraries created with the .dll files are only needed at link time, and then only when importing stuff from a dependency (such as zsh.dll if we do the trick above); we only need to install the .dll files themselves. Maybe someone knows better. -- Peter Stephenson Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070