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, 7 insertions, 0 deletions

diff --git a/src/lib/corelib/language/builtindeclarations.cpp b/src/lib/corelib/language/builtindeclarations.cpp
index ca028cc4f..2f97d7158 100644
--- a/src/lib/corelib/language/builtindeclarations.cpp
+++ b/src/lib/corelib/language/builtindeclarations.cpp
@@ -146,6 +146,9 @@ void BuiltinDeclarations::addDependsItem()
     PropertyDeclaration requiredDecl(QLatin1String("required"), PropertyDeclaration::Boolean);
     requiredDecl.setInitialValueSource(QLatin1String("true"));
     item << requiredDecl;
+    PropertyDeclaration profileDecl(QLatin1String("profiles"), PropertyDeclaration::StringList);
+    profileDecl.setInitialValueSource(QLatin1String("[product.profile]"));
+    item << profileDecl;
     insert(item);
 }
 
@@ -245,6 +248,10 @@ void BuiltinDeclarations::addProductItem()
     decl.setInitialValueSource(QLatin1String("[]"));
     item << decl;
     item << nameProperty();
+    decl = PropertyDeclaration(QLatin1String("profiles"), PropertyDeclaration::StringList);
+    decl.setInitialValueSource(QLatin1String("[project.profile]"));
+    item << decl;
+    item << PropertyDeclaration(QLatin1String("profile"), PropertyDeclaration::String); // Internal
     decl = PropertyDeclaration(QLatin1String("targetName"), PropertyDeclaration::String);
     decl.setInitialValueSource(QLatin1String("name"));
     item << buildDirProperty();