blob: e8ff9bb34acbe7ab6227d95f610d418cde934e5a [file] [log] [blame]
# -------------------------------------------------------------------
# Project file for the QtWebKit C++ APIs
# See 'Tools/qmake/README' for an overview of the build system
# -------------------------------------------------------------------
# Use Qt5's module system
WEBKIT += wtf javascriptcore webcore
build?(webkit1): WEBKIT += webkit1
build?(webkit2) {
WEBKIT += webkit2
have?(QTQUICK): WEBKIT += webkit2qml
# Ensure that changes to the WebKit1 and WebKit2 API will trigger a qmake of this
# file, which in turn runs syncqt to update the forwarding headers.
build?(webkit1): {
build?(webkit2): QMAKE_INTERNAL_INCLUDED_FILES *= WebKit2/Target.pri
use?(3D_GRAPHICS): WEBKIT += angle
MODULE = webkit
CONFIG += creating_module
# This is the canonical list of dependencies for the public API of
# the QtWebKit library, and will end up in the library's prl file.
QT_API_DEPENDS = core gui network
# We want the QtWebKit API forwarding includes to live in the root build dir.
QMAKE_DOCS = $$PWD/qtwebkit.qdocconf
# We load the relevant modules here, so that the effects of each module
# on the QT variable can be picked up when we later load(qt_module).
# Resources have to be included directly in the final binary for MSVC.
# The linker won't pick them from a static library since they aren't referenced.
win* {
RESOURCES += $$PWD/WebCore/WebCore.qrc
include_webinspector {
# WEBCORE_GENERATED_SOURCES_DIR is defined in WebCore.pri, included by
# load(webkit_modules) if WEBKIT contains webcore.
$$PWD/WebCore/inspector/front-end/WebKit.qrc \
# ---------------- Custom developer-build handling -------------------
# The assumption for Qt developer builds is that the module file
# will be put into qtbase/mkspecs/modules, and the libraries into
# qtbase/lib, with rpath/install_name set to the Qt lib dir.
# For WebKit we don't want that behavior for the libraries, as we want
# them to be self-contained in the WebKit build dir.
!production_build: CONFIG += force_independent
# Make sure the install_name of the QtWebKit library point to webkit
force_independent:macx {
# We do our own absolute path so that we can trick qmake into
# using the webkit build path instead of the Qt install path.
CONFIG -= absolute_library_soname
!debug_and_release|build_pass {
# We also have to make sure the install_name is correct when
# the library is installed.
change_install_name.depends = install_target
# The install rules generated by qmake for frameworks are busted in
# that both the debug and the release makefile copy QtWebKit.framework
# into the install dir, so whatever changes we did to the release library
# will get overwritten when the debug library is installed. We work around
# that by running install_name on both, for both configs.
change_install_name.commands = framework_dir=\$\$(dirname $(TARGETD)); \
for file in \$\$(ls $$[QT_INSTALL_LIBS]/\$\$framework_dir/$$BASE_TARGET*); do \
install_name_tool -id \$\$file \$\$file; \
done = install
default_install_target.depends += change_install_name
QMAKE_EXTRA_TARGETS += change_install_name default_install_target
qnx {
# see:
# the gcc 4.4.2 used in the qnx bbndk cannot cope with
# the linkage step of libQtWebKit, adding a dummy .cpp
# file fixes this though - so do this here = dummy.cpp
dummyfile.commands = touch $$