buildroot-novena/package/webkit, branch 2013.02

webkit: fix compilation without X11

2013-01-14T22:51:00+00:00

Fixes: http://autobuild.buildroot.net/results/86534588d192fe1515ce520c109e884864871d94/ and others. Webkit includes X11 headers even when configuerd for DirecfFB, because the test within GNUmakefile.in does not work properly. Autoreconfigure fails because of incompatibility with buildroot's autotools version. For now a patch for GNUmakefile.in fixes this problem. Since webkit release is quite old it doesn't seem to be worth doing more, on the long run we should bump the version. Signed-off-by: Stephan Hoffmann Signed-off-by: Peter Korsgaard

webkit: remove X.org server dependency

2013-01-12T21:53:41+00:00

Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

webkit: fix build with bison 2.6

2012-12-15T20:17:14+00:00

WebKit 1.2.7 does not build with Bison 2.6, but Bison 2.6 is our host-bison, so if the build machine has bison 2.6, or if by chance it gets built before webkit, then the build fails with errors such as: http://autobuild.buildroot.org/results/0b7cfbebd4388cabfa243b5ef74e3b6316fd9fd9/build-end.log (the real error is not visible due to the overwhelming number of warnings). So, we add a patch that modifies WebKit to make it compatible with Bison 2.6 (patch taken from upstream), and we also add 'host-bison' to the WebKit dependencies, so that we are sure that a well-known version of bison is used. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

webkit: silence gazillions of warnings

2012-12-15T18:07:33+00:00

Building webkit with a recent gcc versions gives gazillions of warnings such as 'warning: cast from 'WTF::AlignedBufferChar* {aka char*}' to 'JSC::Identifier*' increases required alignment of target type [-Wcast-align]'. Those make the webkit build very noise, and hard to debug, so let's silence those warnings. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

webkit: Fix build issue with gcc-4.6 and above

2012-10-21T19:22:18+00:00

This fixes the "Unknown parameter for tags/attrs" build error. Backported from commit 88e08c43d0200a4b06a298b7d2541965eebc0afe [PATCH] 2011-04-17 Thierry Reding Reviewed by Adam Barth. Fix build with GCC 4.6. * dom/make_names.pl: Execute preprocessor without the -P option. The preprocessor in GCC 4.6 eats empty lines, effectively breaking the parsing performed by this script. Dropping the -P option when invoking the preprocessor keeps the empty lines but as a side-effect also adds additional linemarkers. From the cpp manpage: -P Inhibit generation of linemarkers in the output from the preprocessor. This might be useful when running the preprocessor on something that is not C code, and will be sent to a program which might be confused by the linemarkers. The linemarkers are not problematic, however, because the script properly handles them by ignoring all lines starting with a #. Signed-off-by: Valentine Barshak Tested-by: Samuel Martin Acked-by: Samuel Martin Signed-off-by: Peter Korsgaard

all packages: rename XXXTARGETS to xxx-package

2012-07-17T18:23:05+00:00

Also remove the redundant $(call ...). This is a purely mechanical change, performed with find package linux toolchain boot -name \*.mk | \ xargs sed -i -e 's/$(eval $(call GENTARGETS))/$(eval $(generic-package))/' \ -e 's/$(eval $(call AUTOTARGETS))/$(eval $(autotools-package))/' \ -e 's/$(eval $(call CMAKETARGETS))/$(eval $(cmake-package))/' Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

package: remove useless arguments from AUTOTARGETS

2011-09-29T21:12:27+00:00

Thanks to the pkgparentdir and pkgname functions, we can rewrite the AUTOTARGETS macro in a way that avoids the need for each package to repeat its name and the directory in which it is present. [Peter: pkgdir->pkgparentdir] Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

webkit: update pthread_getattr_np patches for uClibc 0.9.32

2011-06-24T09:06:35+00:00

Similar to how it is done for qt. Signed-off-by: Peter Korsgaard

webkit: bump to version 1.2.7

2011-03-31T13:23:13+00:00

Signed-off-by: Gustavo Zacarias Signed-off-by: Peter Korsgaard

webkit: prefer X11 backend if both directfb and x11 are available

2011-03-27T20:09:07+00:00

This shouldn't happen with any sane configuration, but is possible with randpackageconfig builds, where it breaks the build as libgtk would prefer X11 and webkit directfb, causing it to fail with: No package 'gtk+-directfb-2.0' found Signed-off-by: Peter Korsgaard