Install bash module prerequisites for amalgamation rather than project

This is similar to what we do for shared libraries in cc::install_rule.

1 files changed, 9 insertions, 2 deletions

diff --git a/build2/bash/rule.hxx b/build2/bash/rule.hxx
index 9957970..5110f97 100644
--- a/build2/bash/rule.hxx
+++ b/build2/bash/rule.hxx
@@ -58,8 +58,12 @@ namespace build2
                          const string&) const;
     };
 
-    // Installation rule for bash scripts (exe{}) and modules (bash{}) that
-    // signals to in_rule that this is update for install.
+    // Installation rule for bash scripts (exe{}) and modules (bash{}). Here
+    // we do:
+    //
+    // 1. Signal to in_rule that this is update for install.
+    //
+    // 2. Custom filtering of prerequisites.
     //
     class install_rule: public install::file_rule
     {
@@ -72,6 +76,9 @@ namespace build2
       virtual recipe
       apply (action, target&) const override;
 
+      virtual const target*
+      filter (action, const target&, const prerequisite&) const override;
+
     private:
       const in_rule& in_;
     };