Re: libtool shouldn't switch to creating static library if it can't create the shared one under Windows

[Marco atzeri]

On 6/17/2011 2:10 AM, Bob Friesenhahn wrote:
> On Fri, 17 Jun 2011, Vadim Zeitlin wrote:
> > Yes, sorry, I keep forgetting about auto-import feature, I guess I'm just
> > too accustomed to the "traditional" Windows way and have trouble
> > accepting
> > auto-import magic. It's true that projects using auto-import could live
> > with falling back to a static library. But consider that
> > auto-importing is
> > relatively new so there should be proportionally few projects using it,
> > hence IMHO the risk of breakage remains reasonably small.
>
> Most projects using libtool come from Unix/Linux where "auto-import" is
> the default so it can be seen that most projects already depend on it
> (and the main issue for them is to use --no-undefined so libtool will
> build a DLL). Primarily programs which originated under Windows (or
> really care about Windows) use the dllexport/dllimport facilities.
>
> Bob

Bob, Vadim,
on cygwin

"lt_cv_deplibs_check_method=pass_all"

is my workaround at configure stage to bypass incorrect
libtool detection of system capabilities and to allow
shared libs building.

It made me crazy building octave where the
DLL dependency list is very very long.

Regards
Marco