diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2016-08-24 15:41:54 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2016-08-24 15:41:54 +0200 |
| commit | 3a8972b42f75e10e9a833bba58d65009e7bed7f3 (patch) | |
| tree | cb350e533b967b828ece6a59ced5bb2caa932de7 /build2/cc/init.cxx | |
| parent | feb55ebfdc536c32de2c173d108df5ee0004da44 (diff) | |
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
Diffstat (limited to 'build2/cc/init.cxx')
| -rw-r--r-- | build2/cc/init.cxx | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/build2/cc/init.cxx b/build2/cc/init.cxx index 474db70..0c82169 100644 --- a/build2/cc/init.cxx +++ b/build2/cc/init.cxx @@ -52,7 +52,7 @@ namespace build2 v.insert<strings> ("cc.export.poptions"); v.insert<strings> ("cc.export.coptions"); v.insert<strings> ("cc.export.loptions"); - v.insert<strings> ("cc.export.libs"); + v.insert<names> ("cc.export.libs"); // Hint variables (not overridable). // |