On Sat, 2008-10-11 at 17:00 +0200, Christian Hoff wrote: > > cygwin is a obsolete tool. The future is mingw. I use atotools in > > mingw, but auto* really suck in windows or linux.
I'm not really interested in the old auto* sucks debate. It does and it doesn't. I have a love/hate relationship with it. As far as cygwin being obsolete, I don't really care whether people use cygwin or mingw or whatever. The point is that there are auto* toolchains available on win32 and they work. > The question for me is not how much time it takes to install Cygwin; > Cygwin simply hides the aspect that this build system is not portable. > Without Cygwin there would be no way to compile Gtk# with the existing > build system. The build system is portable. I don't understand why you contend it isn't when the toolchain is available on linux, win32, and mac platforms. If by unsupported you mean it has to be downloaded and installed, are you arguing that the .Net SDK is unsupported on win32? > I will look into both CMake and waf and see if I manage to build Gtk# > with them. By now I haven't got an idea how they work, but in every case > I don't think that the auto* build system is the best choice. I'll keep > you posted. Either of these would have to produce some tangible benefit to the project over what the auto* build does now in order for me to consider switching from the standard build environment on the primary development platform of the project. I haven't heard anything so far that leads me to believe that's the case. -- Mike Kestner <[EMAIL PROTECTED]> _______________________________________________ Gtk-sharp-list maillist - Gtk-sharp-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/gtk-sharp-list
