From 3a8972b42f75e10e9a833bba58d65009e7bed7f3 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Wed, 24 Aug 2016 15:41:54 +0200 Subject: Handle *.export.libs, distinguish interface and implementation dependencies A library dependency on another libraries is either "interface" or "implementation". If it is interface, then everyone who links to this library should also link to the interface dependency, explicitly. A good example of an interface dependency is a library API that is called in inline functions. Interface dependencies of a library should be explicitly listed in the *.export.libs (where we can also list target names). So the typical usage will be along these lines: import int_libs = libfoo%lib{foo} import int_libs += ... import imp_libs = libbar%lib{bar} import imp_libs += ... lib{baz}: ... $int_libs $imp_libs lib{baz}: cxx.export.libs = $int_libs --- build2/utility.ixx | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'build2/utility.ixx') diff --git a/build2/utility.ixx b/build2/utility.ixx index 956a726..36c7a7f 100644 --- a/build2/utility.ixx +++ b/build2/utility.ixx @@ -42,6 +42,13 @@ namespace build2 template inline void + append_options (strings& args, T& s, const variable& var) + { + append_options (args, s[var]); + } + + template + inline void append_options (cstrings& args, T& s, const char* var) { append_options (args, s[var]); @@ -49,6 +56,13 @@ namespace build2 template inline void + append_options (strings& args, T& s, const char* var) + { + append_options (args, s[var]); + } + + template + inline void hash_options (sha256& csum, T& s, const variable& var) { hash_options (csum, s[var]); -- cgit v1.1