From 261966dbb73fec54ed1a460f88cf44e1a8478d83 Mon Sep 17 00:00:00 2001 From: Tobias Hunger Date: Mon, 15 Feb 2010 17:33:56 +0100 Subject: Have qmakestep trigger the import label * Do not use the BuildManager but have the qmakestep trigger the update via the target and project. Reviewed-by: dt --- src/plugins/qt4projectmanager/qt4buildconfiguration.h | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'src/plugins/qt4projectmanager/qt4buildconfiguration.h') diff --git a/src/plugins/qt4projectmanager/qt4buildconfiguration.h b/src/plugins/qt4projectmanager/qt4buildconfiguration.h index 08c032d8ba..3846e587ff 100644 --- a/src/plugins/qt4projectmanager/qt4buildconfiguration.h +++ b/src/plugins/qt4projectmanager/qt4buildconfiguration.h @@ -86,6 +86,9 @@ public: // used by qmake step to notify that the qmake args have changed // not really nice void emitQMakeBuildConfigurationChanged(); + // used by qmake step to notify that the build directory was initialized + // not really nice + void emitBuildDirectoryInitialized(); void getConfigCommandLineArguments(QStringList *addedUserConfigs, QStringList *removedUserConfigs) const; // Those functions are used in a few places. @@ -120,6 +123,8 @@ signals: /// configuration changed void targetInformationChanged(); + void buildDirectoryInitialized(); + private slots: void qtVersionsChanged(const QList &changedVersions); -- cgit v1.2.1