[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cygwin dlopening backends
From: |
Ralf Wildenhues |
Subject: |
Re: cygwin dlopening backends |
Date: |
Sun, 13 Nov 2005 23:09:43 +0100 |
User-agent: |
Mutt/1.5.9i |
Hi Charles,
Thank you for the feedback!
* Charles Wilson wrote on Sun, Nov 13, 2005 at 06:42:06AM CET:
>
> Basic libtool-HEAD with this patch on cygwin (compiling in both dlopen
> and loadlibrary loaders) compiles and passes all expected tests in the
> suite.
*snip*
> So it seems that, from a functional standpoint, Ralf's patch addresses
> all of points (1), (2), and (3) from his earlier post.
Great!
> That just leaves Eric's comments, and Ralf's point (4). I wonder if it
> would be a good idea to add --enable/--disable configure flags for every
> loader...with the "default" set of loaders determined on a per-platform
> basis. That's the most flexible (and wouldn't be a cygwin-specific
> hack), but it seems like it could be really complicated.
I postponed that part on purpose. The ever-increasing number of
configure switches is frightening. OTOH, choice is good in this case,
IMVHO. Maybe we can get away with one switch for all of them. Like
this:
--disable-ltdl-loaders=LOADER[,...]
But there actually is another point I forgot to mention:
(3a) if both dlopen and LoadLibrary are used on cygwin, the former
_must_ be tried first by ltdl. I believe you mentioned that this
is not the case ATM (haven't checked yet).
I would really like to fix them in order, i.e., fix (4) last.
Cheers,
Ralf
Re: cygwin dlopening backends, Charles Wilson, 2005/11/13