Instead use the same logic as in libgtk2. The rendering target selected
MUST be the same as libgtk2's, so just figure it out automatically
instead.
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
libgtk2 can either use the X11 or directfb backend, depending on what
is selected - But if other packages 'select' libgtk2 there is no
guarantee that any backends are enabled, breaking the build.
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
I could have created a !dependency on !BR2_PTHREADS_OLD, but that
wouldn't work with external toolchains. So, let's just add a notice in
the help message of WebKit.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Webkit currently depends on libgtk2, which itself depends on
Cairo. However, the dependency of libgtk2 is only on
BR2_PACKAGE_CAIRO, BR2_PACKAGE_CAIRO_PS and
BR2_PACKAGE_CAIRO_PDF. While this might be enough for libgtk2 to build
and work, Webkit makes direct use of the PNG functionnalities of
Cairo. If this functionnality is not available in Cairo, the Webkit
build complains that cairo_surface_write_to_png_stream() is not
defined.
Therefore, we make sure that WebKit selects BR2_PACKAGE_CAIRO_PNG.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Closes#427
- Fix generation of configure script and Makefiles.
- Add dependencies on libsoup and enchant.
- Allow configuration of rendering target (currently X11 or DirectFB).
Signed-off-by: Will Newton <will.newton@gmail.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Peter Korsgaard
Thomas Petazzoni
Will Newton
Ulf Samuelsson
John Voltz