[Gtk-sharp-list] Migrating to CMake?

Christian Hoff christian_hoff at gmx.net
Sat Oct 11 11:00:45 EDT 2008

Martin (OPENGeoMap) schrieb:
> hi:
>> On Sat, 2008-10-11 at 13:37 +0200, Christian Hoff wrote:
>>> in my opinion the current build process does not suit Gtk# and a 
>>> cross-platform project in general. The autotools/make build system 
>>> is simply not portable; Windows users have to install either a 
>>> Cygwin build environment or create their own Makefiles(as I finally 
>>> did).
>> I just installed cygwin on my new laptop for an installer summit we're
>> having this weekend and had things set up and building with little
>> effort.  I spent more time downloading and setting up .Net framework
>> than anything related to cygwin/gtk+.  I am _far_ from a windows
> cygwin is a obsolete tool. The future is mingw. I use atotools in 
> mingw, but auto* really suck in windows or linux.
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.
>> development guru.  The wiki articles at mono-project.com and medsphere
>> document the wrinkles.  I don't see the problem.
>>> I think we need a cross-platform build process and thought about 
>>> migrating to CMake. CMake runs natively on all important 
>>> platforms(including MacOS) and seems to fulfill our needs(it does 
>>> even support cross-platform compilation!). The gapi-cdecl-insert 
>>> script can be replaced by a sed command as I did in the MinGW 
>>> makefiles already. What do you think? Is my idea actually possible? 
>>> I would start working on it if you want.      
> There are obsolete technologies in linux and people don´t mind that. I 
> believe we have go ahead...
> With waf you can compile in a easy way software for visual c++, mingw, 
> gcc, mono, D, java, Qt, GTK, gnome, KDE,...
> Like WAF in python we can hack it really easy. We can add support to 
> IDEs workspace like code-blocks, netbeans, monodevelop, visual studio, 
> etc
> by default WAF works like auto*. CMAKE create workspaces for default 
> in windows.
> Regards.
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.


More information about the Gtk-sharp-list mailing list