aboutsummaryrefslogtreecommitdiff
path: root/build/cli/module.cxx
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2015-11-30 15:28:07 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2015-11-30 15:28:07 +0200
commited79e798327c9d18c2b5b2dfea8ad98b4d69f883 (patch)
tree0b10baec0f9a9ea466ff782a7cbb4fdd2973a031 /build/cli/module.cxx
parentd5e4d325c6a4acc8df6f0e42bc7d76e1f833d58a (diff)
Tighten unresolved group logic
Now a wildcard/fallback rule should explicitly detect and handle unresolved situation.
Diffstat (limited to 'build/cli/module.cxx')
-rw-r--r--build/cli/module.cxx6
1 files changed, 6 insertions, 0 deletions
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.