From ee0456ed4a5f3f6686fbb0a433161d1f9d8535fe Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Thu, 4 Jul 2019 07:30:23 +0200 Subject: 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{*} --- build2/cc/utility.hxx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'build2/cc/utility.hxx') diff --git a/build2/cc/utility.hxx b/build2/cc/utility.hxx index 80ca741..6222b5f 100644 --- a/build2/cc/utility.hxx +++ b/build2/cc/utility.hxx @@ -58,7 +58,7 @@ namespace build2 } // Given the link order return the library member to link. That is, liba{} - // or libs{} for lib{} and libue{}, libua{} or libus{} for libu*{}. + // or libs{} for lib{} and libua{} or libus{} for libul{}. // // If existing is true, then only return the member target if it exists // (currently only used and supported for utility libraries). -- cgit v1.1