From 9034f7c51ef6437ce9d4547ba5bde217b4740fb2 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Tue, 19 Apr 2022 11:10:53 +0200
Subject: Use target recipe for auxiliary data storage during match-apply

In particular, we now have separate auxiliary data storage for inner
and outer operations.
---
 libbuild2/cc/compile-rule.hxx | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'libbuild2/cc/compile-rule.hxx')

diff --git a/libbuild2/cc/compile-rule.hxx b/libbuild2/cc/compile-rule.hxx
index 16b33fa..49d33eb 100644
--- a/libbuild2/cc/compile-rule.hxx
+++ b/libbuild2/cc/compile-rule.hxx
@@ -44,6 +44,8 @@ namespace build2
                                                dyndep_rule
     {
     public:
+      struct match_data;
+
       compile_rule (data&&, const scope&);
 
       virtual bool
@@ -53,7 +55,7 @@ namespace build2
       apply (action, target&) const override;
 
       target_state
-      perform_update (action, const target&) const;
+      perform_update (action, const target&, match_data&) const;
 
       target_state
       perform_clean (action, const target&) const;
@@ -74,7 +76,6 @@ namespace build2
       functions (function_family&, const char*); // functions.cxx
 
     private:
-      struct match_data;
       using environment = small_vector<const char*, 2>;
 
       template <typename T>
-- 
cgit v1.1