From d6d2074ffedd47561a5ca4afe48a7ed816d4e595 Mon Sep 17 00:00:00 2001 From: Thiago Macieira Date: Wed, 3 Oct 2012 15:07:59 -0700 Subject: Do not use an export macro in the function definition qmlExecuteDeferred is exported using Q_DECLARATIVE_EXPORT in qdeclarative.h, so we don't need to use one here. Better not have any than have the wrong one, which can cause problems. Change-Id: I672f8aaf0fef2600a6ab8c4a17112404fc5b1cda Reviewed-by: Lars Knoll Reviewed-by: Olivier Goffart --- src/declarative/qml/qdeclarativeengine.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src') diff --git a/src/declarative/qml/qdeclarativeengine.cpp b/src/declarative/qml/qdeclarativeengine.cpp index 45483873..3f574065 100644 --- a/src/declarative/qml/qdeclarativeengine.cpp +++ b/src/declarative/qml/qdeclarativeengine.cpp @@ -1019,7 +1019,7 @@ QDeclarativeEngine::ObjectOwnership QDeclarativeEngine::objectOwnership(QObject return ddata->indestructible?CppOwnership:JavaScriptOwnership; } -Q_AUTOTEST_EXPORT void qmlExecuteDeferred(QObject *object) +void qmlExecuteDeferred(QObject *object) { QDeclarativeData *data = QDeclarativeData::get(object); -- cgit v1.2.3