The mailing list thread can be found at . Currently we have two issues:
1. how should we go about non-recursive make?
2. The directory has a few Makefiles lying around for the mac port. How are going to deal with this? Can we put our build artifacts in a separate build directory?
Created attachment 17830 [details]
initial configure.ac implementation
initial implementation based on gtk-webcore's configure.ac.
I think naming our ac makefiles with a gtk suffix, like you did in the configure is enough. Did you write any Makefile.gtk.ac also?
We should probably enable *_DISABLE_DEPRECATED when in --maintainer-mode as per bug #16353.
Created attachment 17902 [details]
I also named it GNUmakefile.am instead of Makefile.am to avoid overwriting the (mac) 'Makefile's. If you are using GNU Make in mac but want to use the mac Makefile, make sure you use '-f Makefile' as GNUmakefile takes precedence over Makefile.
Appreciate any feedback or suggestion you might have. Cheers!
Created attachment 17907 [details]
Everything works fine with freetype2 9.15.3 and fontconfig 2.4.2, we can lower the requirements.
What about numbering next patches without making previous obsolete?
Created attachment 17914 [details]
Subject: [PATCH] Lower even more the requirements.
Explicitely use automake-1.9 if available.
Do not call autoreconf in autogen.sh (!?).
autogen.sh | 31 ++++++++++++++++++++++++++++---
configure.ac | 4 ++--
2 files changed, 30 insertions(+), 5 deletions(-)
Created attachment 17925 [details]
support build directories and merge GNUmakefile.ams
This updated patch should allow one to build JSC (atm) in a build directory. You have to 'cd' in the build tree and call autogen.sh and configure from there though. It also merges all GNUmakefile.am in JSC into one JSC/GNUmakefile.am.
I should point to the jsc-modular build system that is a fixed up out-of-tree autotools build system for jsc with no gtk+ etc. dependency:
Created attachment 18054 [details]
JSC and WebKitGtk+ library builds
Things that are not done yet (appreciate any help to speed up things a bit):
1. GtkLauncher and DRT build
2. make install, dist, clean, and possibly check
3. DirectFB, win32, and GtK/OSX builds
4. build-webkit and at least run-webkit-tests (DRT?) autotool support
Also, I haven't tested the different features. One more issue is that since we have a lot of autogenerated sources, IDL/JS bindings in particular, it would be nice if we can timestamp those files to avoid rebuilding the whole thing in "make all".
Appreciate any feedback or patch you might have. Cheers.
Also just use --srcdir in configure and point it to the webkit tree if you want to build in a different directory (build/ dir for example).
Created attachment 18055 [details]
updated patch without a commented BUILT_SOURCES
Created attachment 18118 [details]
Updated patch includes GtkLauncher and DRT build configs. All features (incl. SVG features) were tested except for XBL and Coverage support.
Appreciate any feedback you might have here. Also, to install a stripped down library, use install-strip instead of install.
Created attachment 18122 [details]
updated patch to fix the ChangeLogs and code coverage flag
This patch fixes the redundancy in the ChangeLogs from the previous patch. Also fixes the coverage flag errors detected by autoconf and make.
Created attachment 18123 [details]
indentation and cleanups
As per suggestions by alp:
Indentation fixes and removal of some header/func checks and credit/copyright in configure.ac. Also fix generation of webkitgtk.pc and Changelog fixes.
Comment on attachment 18123 [details]
indentation and cleanups
Will remove some of the verbose comments as discussed (and a couple of minor typofixes) before landing.
Landed in r28997.