diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2018-07-21 16:33:07 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2018-07-21 16:33:07 +0200 |
commit | 063b1a3c038ace6e1d9f8c49c04bf82dd9034828 (patch) | |
tree | 34ad2bcb78197256e6492332eb1b8187e02d81da /build2/install | |
parent | 77cf6f1cd3cdaa5c84ca191ad03d58b6355821fc (diff) |
Install bash module prerequisites for amalgamation rather than project
This is similar to what we do for shared libraries in cc::install_rule.
Diffstat (limited to 'build2/install')
-rw-r--r-- | build2/install/rule.hxx | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/build2/install/rule.hxx b/build2/install/rule.hxx index 20b30a1..1ce2830 100644 --- a/build2/install/rule.hxx +++ b/build2/install/rule.hxx @@ -27,7 +27,7 @@ namespace build2 // target otherwise. The default implementation accepts all prerequsites // from the target's (weak) amalgamation. // - // The prerequisite it passed as an iterator allowing the filter to + // The prerequisite is passed as an iterator allowing the filter to // "see" inside groups. // using prerequisite_iterator = @@ -105,7 +105,11 @@ namespace build2 // target otherwise. The default implementation ignores prerequsites // that are outside of this target's project. // - // The prerequisite it passed as an iterator allowing the filter to + // @@ I wonder why we do weak amalgamation for alias but project for + // file? And then override this for prerequisite libraries/modules + // in cc::install_rule and bash::install_rule... + // + // The prerequisite is passed as an iterator allowing the filter to // "see" inside groups. // using prerequisite_iterator = |