|
From: Earnie <ea...@us...> - 2010-08-25 15:31:10
|
Jasper Horn wrote: > Earnie wrote: > >> Your concern for loss of users is honorable. But are we loosing them >> over the lack of an installer of GCC 4 or the lack of 64 bit support? > > Well, I started a conversation about the other possibility not too > long ago, and unfortunately it turned out that taking steps to work > together with mingw64 more closely were generally regarded as a lot of > effort (and changes in general some people were not ready to make) and > too many people did not see an eventual merger of the projects > happening (which, in my eyes should be the ultimate goal, even if it > takes several years more of cooperation, before it will be possible). > > Either way, I have a feeling that the installer is a bigger problem > the 64 bit support, but I may be wrong about that. > How many years has 64 bit Windows been available? We are that many years behind. The mingw-w64 project is providing both a backward compatible Win32 as well as a Win64 versions of MinGW with multilib support they are miles ahead of us. I'm all for a cooperative spirit and what they have going is good. The fork happened because the originator needed to move quicker than we were allowing him because of constraints from his employer. Not a bad thing but the bigger problem was a communication gap. I am monitoring the users list and participating in conversations their. Especially in regard to the use of MSYS. >> We can update the mingw.ini file that controls the current installer but >> we need someone to maintain it. Maintaining it would require watching >> for updates to packages, modifying the mingw.ini file and submitting the >> changes to CVS. > > I am currently looking updating it. I am not making any promises about > maintaining it yet, though (even providing gcc 4.5.0 while 4.5.1 is > out is better than providing only gcc 3 installations in my opinion). > It will be good if you can make it happen. -- Earnie -- http://www.for-my-kids.com |