|
From: | Guido Draheim |
Subject: | Re: "Re: libbfd, libtool & Win32" and "Re: Building a MinGW GLib etc..." |
Date: | Tue, 17 Sep 2002 00:51:27 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 |
Bob Friesenhahn wrote:
On Mon, 16 Sep 2002, Max Bowsher wrote:There is one major decision that needs to be made: Keep or remove support for old versions of the mingw toolchain. All the -mdll stuff is deprecated in favour of gcc -shared now.Since MinGW itself is a work in progress, I recommend that support for pre "gcc -shared" toolchains be removed. Support should be as similar to Cygwin as possible, while ensuring that there are no DLL conflicts. My experience is that current CVS libtool does not work acceptably under MinGW so I think that the current stuff should be discarded in favor of working code.
ho ho ho, I was even thinking of patching libtool-1-4 branch. And I use crossmingw in a production environment at my employer, so changes in the build environment usually take effect within the next two year after releasing new generations, - however, I can sell an update-version much better than great new stuff, taking effect within months.
I can test the updated libtool with ImageMagick, which should exercise it pretty well under MinGW.
I have some libs too that I crosscompile regularly. Whatever we come up with patches, I am very sure it can be tested thoroughly - I did just have a look on to mingw-users ML, and I was amazed about the traffic over there... wasn't that different a year back? Is that another XP effect taking place?
[Prev in Thread] | Current Thread | [Next in Thread] |