Re: libltdl exports no symbols (cygwin)

[Ralf Wildenhues]

Hi Chuck,

* Charles Wilson wrote on Sun, Jan 28, 2007 at 08:35:11PM CET:
> Ralf Wildenhues wrote:
> 
> >>This patch is against CVS on branch-1-5.  I'll follow up with a similar 
> >>patch for HEAD.
> 
> Sorry that *I* dropped the ball on a forward port to HEAD.

No worries.

> >I am a bit wary that it may cause regressions in users' packages, as
> >they may be using LT_SCOPE.  But I see that with the other change, this
> >is needed.
> 
> User-package use of internal libtool macros (e.g. LT_SCOPE) is outside 
> libtool's control.

Hmm, yes.  I've never been certain whether LT_SCOPE was *intended* to be
purely internal, or for the user to use.  The latter seems inappropriate
to me now, but I don't think people were aware of this all the time.

Eventually, we should do something about this by offering a portable way
to decorate imports/exports for users of libtool.  Not right now.

> >I'm still wondering what to put in NEWS for this and the depending
> >change.  We should mention this somehow.  Suggestions appreciated.
> 
> "Fix regression in libltdl symbol exports on Cygwin. Side effect: 
> LT_GLOBAL_DATA and LT_SCOPE are now explicitly defined as 
> declspec(dllexport), bypassing auto-export logic on Cygwin.  This tracks 
> existing behavior on MinGW."

Thanks, that's good enough for me; applied to both branches.
Thanks also for checking the patch.

> I try to avoid hardcoding my actual email address (or alias) on archived 
> mailing lists. Plus, I'm more likely to see/read a libtool-related 
> message from an unrecognized source if it appears on a mailing list that 
> I monitor; direct messages from unrecognized sources are likely to get 
> caught in my heavy spam filtering.  But do as you will (just refrain 
> from re-posting the "updated" ChangeLog header, next time).

OK, done this time.  I'll try to remember it.

Cheers,
Ralf