From ed79e798327c9d18c2b5b2dfea8ad98b4d69f883 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Mon, 30 Nov 2015 15:28:07 +0200
Subject: Tighten unresolved group logic

Now a wildcard/fallback rule should explicitly detect and handle unresolved
situation.
---
 build/cli/module.cxx | 6 ++++++
 1 file changed, 6 insertions(+)

(limited to 'build/cli')

diff --git a/build/cli/module.cxx b/build/cli/module.cxx
index 05abb94..64e95a8 100644
--- a/build/cli/module.cxx
+++ b/build/cli/module.cxx
@@ -72,6 +72,12 @@ namespace build
 
         rs.insert<cxx::ixx> (perform_id, update_id, "cli", compile_);
         rs.insert<cxx::ixx> (perform_id, clean_id, "cli", compile_);
+
+        // Other rules (e.g., cxx::compile) may need to have the group
+        // members resolved. Looks like a general pattern: groups should
+        // resolve on configure(update).
+        //
+        rs.insert<cli_cxx> (configure_id, update_id, "cli", compile_);
       }
 
       // Enter module variables.
-- 
cgit v1.1