The original approach does not work with absolute file paths on Windows
Change-Id: I9f284dfa7c0fe145a99e216a571d3f0eb1289f94
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
The check that was done in there was problematic for two reasons:
- It encoded a policy that a file could not be deployed to more than
one target path, which might not always be true.
- It made the function unexpectedly expensive, resulting in
quadratic behavior for repeated calls. This resulted in noticeable
UI lag when loading larger projects.
It's the caller's responsibility to prevent duplicates.
Task-number: QTCREATORBUG-18533
Change-Id: I33a328b14f95fe84b3c1041d4b74d645946250bb
Reviewed-by: hjk <hjk@qt.io>
If the deployment configuration contains an "install into temp dir"
step, then the local file paths of the binaries built by the build tool
will not be in the list of deployable files, because all deployables
come from the temporary install dir. Therefore, look for just a file
name match as a fallback.
Fixes: QTCREATORBUG-21235
Change-Id: Ie3fad515515b4f28cc6bdef1254f4c05a0557569
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
More in line with QFileInfo terminonlogy which appears to be
best-of-breed within Qt.
Change-Id: I1d051ff1c8363ebd4ee56376451df45216c4c9ab
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
We use the same approach as for CMake, namely the
QtCreatorDeployment.txt file.
Fixes: QTCREATORBUG-19202
Change-Id: I50605b8236b26f0c911e2448330019e94753af19
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: hjk <hjk@qt.io>
We will add more code to the DeploymentData class, and we don't want it
all to be inline.
Change-Id: I5d51d5d44078e6a38262925be21d447ebd8f629e
Reviewed-by: hjk <hjk@qt.io>
