From 6a2ecb47b9e3c78e7c947549d7d3aff2a903a5fe Mon Sep 17 00:00:00 2001 From: Jocelyn Turcotte Date: Thu, 20 Feb 2014 16:24:09 +0100 Subject: Do not disable RTTI for module libraries This would prevent QWebEnginePage to be subclassed in applications built with RTTI enabled. We don't need this anymore since all classes inherited from exported core classes are pure virtual and completely defined in their header. Change-Id: I4ce19f893626e9bcb5cd4b11b7264e43ddcbac31 Reviewed-by: Andras Becsi --- tools/qmake/mkspecs/features/default_pre.prf | 5 ----- 1 file changed, 5 deletions(-) (limited to 'tools/qmake') diff --git a/tools/qmake/mkspecs/features/default_pre.prf b/tools/qmake/mkspecs/features/default_pre.prf index e2ae92cdb..843188923 100644 --- a/tools/qmake/mkspecs/features/default_pre.prf +++ b/tools/qmake/mkspecs/features/default_pre.prf @@ -3,11 +3,6 @@ QTWEBENGINE_ROOT = $$replace(PWD, /tools/qmake/mkspecs/features$,) QTWEBENGINEPROCESS_NAME = QtWebEngineProcess -# Tweaks that shouldn't affect our examples -!contains(_PRO_FILE_PWD_, $$QTWEBENGINE_ROOT/examples) { - # We have to disable RTTI for now since that's how chromium builds on linux - unix:QMAKE_CXXFLAGS += -fno-rtti -} # Location of sync.profile MODULE_BASE_DIR = $$QTWEBENGINE_ROOT -- cgit v1.2.3