ProjectExplorer/QNX: Add build step for checking device existence

This introduces a DeviceCheckBuildStep which any DeployConfigurationFactory
could use to insert a step to check whether a device is set up for the
current kit or not. Currently only used in the QNX deploy configuration.

If there is no device known to a QNX kit, ask the user
to add one. Launch the appropriate device wizard if the user agrees
to add a device.

Change-Id: I42db995f50890e2a2dd7aacc24a0049cdd6a6fee
Reviewed-by: Christian Kandeler <christian.kandeler@digia.com>
This commit is contained in:
Tobias Nätterlund
2013-05-30 14:31:41 +02:00
committed by Tobias Nätterlund
parent 316b9a36e9
commit cbb6db1232
6 changed files with 197 additions and 4 deletions

View File

@@ -35,6 +35,7 @@
#include "qnxdeployconfiguration.h"
#include "qnxdeviceconfigurationfactory.h"
#include <projectexplorer/devicesupport/devicecheckbuildstep.h>
#include <projectexplorer/kitinformation.h>
#include <projectexplorer/target.h>
#include <remotelinux/genericdirectuploadstep.h>
@@ -77,7 +78,9 @@ ProjectExplorer::DeployConfiguration *QnxDeployConfigurationFactory::create(Proj
ProjectExplorer::DeployConfiguration * const dc = new QnxDeployConfiguration(parent, id,
displayNameForId(id));
dc->stepList()->insertStep(0, new RemoteLinux::GenericDirectUploadStep(dc->stepList(),
dc->stepList()->insertStep(0, new ProjectExplorer::DeviceCheckBuildStep(dc->stepList(),
ProjectExplorer::DeviceCheckBuildStep::stepId()));
dc->stepList()->insertStep(1, new RemoteLinux::GenericDirectUploadStep(dc->stepList(),
RemoteLinux::GenericDirectUploadStep::stepId()));
return dc;
}