GNOME Bugzilla – Bug 532353
Consider switching to waf from autotools
Last modified: 2016-08-18 12:22:24 UTC
It'd be nice to switch to a sane build system, and waf might be such a system. I'll attach a wscript that can be tossed into the metacity directory and one can then build metacity using waf configure [--prefix DIR] waf [build] I haven't yet tested: waf install However, this is only preliminary; my wscript is far from complete and there's a few gotchas too: - No user-conditional compilation (e.g. --disable-compositor), except with gconf - No existence-conditional compilation; the build fails if libraries don't exist - Does not do translations - Installation completely untested - There's a dependency issue: with a clean project (e.g. after 'waf clean' or before ever running waf) the command waf build --target metacity will fail because the inlinepixbufs.h target never gets generated.
Created attachment 110644 [details] preliminary waf script for building metacity
Oh, and the script only works if you delete src/ui/colors.[ch] which are unused source files with compilation issues. Those will soon be nuked from svn, though...
Note that there's a regression in waf-1.4.1 which prevents this wscript from working. You'll need to use waf <= 1.4.0 (jhbuild installs 1.3.2 for now), or remove the ui/ and core/ prefixes on files in the "excludes" argument to find_sources_in_dirs. (gjc and others thought it was just an API change, but ita in irc said it was unintentional and a regression.)
you can also have a look into cheese or packagekit, where we already have working waf scripts
Hello Elijah, any news about these waf scripts? :) Here a list with GTK+/Gnome projects that already use waf, maybe it helps: http://live.gnome.org/JavierJardon/NewBuildSystem Regards