diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2019-07-04 07:30:23 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2019-07-04 07:30:23 +0200 |
commit | ee0456ed4a5f3f6686fbb0a433161d1f9d8535fe (patch) | |
tree | 697834b68df162a004a6e13113260a11e0236af6 /build2/bin/init.cxx | |
parent | f52b47eea4c5de553d202669f91e6f4f14668592 (diff) |
Remove libu{} target group
The semantics provided by libu{} is rarely required and as result was not
yet documented. However, if you are using it, the new way to achieve the
same result is to use both libue{} and libul{} explicitly, for example:
exe{foo}: libue{foo}
lib{foo}: libul{foo}
{libue libul}{foo}: cxx{*}
Diffstat (limited to 'build2/bin/init.cxx')
-rw-r--r-- | build2/bin/init.cxx | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/build2/bin/init.cxx b/build2/bin/init.cxx index 37fad6b..5932b29 100644 --- a/build2/bin/init.cxx +++ b/build2/bin/init.cxx @@ -439,7 +439,9 @@ namespace build2 t.insert<hbmia> (); t.insert<hbmis> (); +#if 0 t.insert<libu> (); +#endif t.insert<libul> (); t.insert<libue> (); t.insert<libua> (); @@ -516,9 +518,6 @@ namespace build2 r.insert<hbmi> (perform_update_id, "bin.hbmi", fail_); r.insert<hbmi> (perform_clean_id, "bin.hbmi", fail_); - r.insert<libu> (perform_update_id, "bin.libu", fail_); - r.insert<libu> (perform_clean_id, "bin.libu", fail_); - r.insert<libul> (perform_update_id, "bin.libul", fail_); r.insert<libul> (perform_clean_id, "bin.libul", fail_); |