Make it possible to set profiles per product.

Use case 1: Build product A for architecture X and product B
for architecture Y (e.g. host tools vs target libraries).
Use case 2: Build product A for architectures X and Y and
product B only for architecture X (e.g. Android
multi-arch packages).

Change-Id: I2eb721c37cdd12c298ee12bad60e21e94b04676b
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/src/lib/corelib/buildgraph/inputartifactscanner.cpp b/src/lib/corelib/buildgraph/inputartifactscanner.cpp
index 0f6161235..b75184597 100644
--- a/src/lib/corelib/buildgraph/inputartifactscanner.cpp
+++ b/src/lib/corelib/buildgraph/inputartifactscanner.cpp
@@ -364,7 +364,7 @@ void InputArtifactScanner::handleDependency(ResolvedDependency &dependency)
         ResolvedProduct * const otherProduct = artifactDependency->product;
         if (m_logger.traceEnabled()) {
             m_logger.qbsTrace() << "[DEPSCAN] add artifact dependency " << dependency.filePath
-                                << " (from product " << otherProduct->name << ')';
+                                << " (from product " << otherProduct->uniqueName() << ')';
         }
         insertIntoProduct = false;
     }