Re: cygwin dlopening backends

[Charles Wilson]

Ralf Wildenhues wrote:
> Hi Charles,
>
> > 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[,...]

that sounds good.  Have no idea how it should be implemented tho.

> 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).

No, I think the wrong-order problem was because of my (now abandoned) 
patch when packaging libtool for the cygwin distribution.  I *believe* 
the current impl, when both loaders are compiled in, calls dlopen first. 
  But I'll check...

> I would really like to fix them in order, i.e., fix (4) last.

Sure.

--
Chuck