Date: Tue, 20 Nov 2007 10:41:56 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Announce: FlexDLL, flexible DLLs under Windows
Message-ID: <20071120154156.GA23663@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4742E7F7 DOT 8000400 AT frisch DOT fr> <057201c82b84$98ee9870$2e08a8c0 AT CAM DOT ARTIMI DOT COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <057201c82b84$98ee9870$2e08a8c0@CAM.ARTIMI.COM>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Tue, Nov 20, 2007 at 02:49:48PM -0000, Dave Korn wrote:
>On 20 November 2007 13:58, Alain Frisch wrote:
>
>> Dear Cygwin and MinGW mailing lists,
>> 
>> I'd like to announce the availability of FlexDLL, a new tool that should
>> greatly help porting some Unix applications under Windows. FlexDLL
>> implements the classical POSIX dlopen API. In short, it lets you create
>> DLLs with unresolved symbols. 
>
>> Feedback and comments are very welcome!
>
>  This looks very interesting indeed.  The technique of turning unresolved
>imports into data items that can be fixed up at runtime thus letting the
>windows runtime loaded accept the dll is a clever trick, and it occurs to me
>that it might be worth adopting the same technique directly in the binutils
>toolchain itself.
>
>  Thanks for your valuable contribution!

Indeed, this is very interesting.  It sounds a little like the
autoload.cc code in Cygwin which handles optional linking from dlls but it
is obviously much more advanced.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/