|
From: | Bob Friesenhahn |
Subject: | Re[3]: libtool shouldn't switch to creating static library if it can't create the shared one under Windows |
Date: | Thu, 16 Jun 2011 19:10:39 -0500 (CDT) |
User-agent: | Alpine 2.01 (GSO 1266 2009-07-14) |
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 Friesenhahn address@hidden, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
[Prev in Thread] | Current Thread | [Next in Thread] |