aboutsummaryrefslogtreecommitdiff
path: root/build2/cc/init.cxx
AgeCommit message (Collapse)AuthorFilesLines
2016-08-26Add pkg-config support for import installedBoris Kolpackov1-0/+20
Redesign library importing/exporting while at it.
2016-08-24Pick *.libs variable depending on library type during static linkingBoris Kolpackov1-0/+7
2016-08-24Handle *.export.libs, distinguish interface and implementation dependenciesBoris Kolpackov1-1/+1
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
2016-08-23Add cc.config in addition to ccBoris Kolpackov1-19/+56
2016-08-23Rename cc.{vars,config} modules to cc.core.{vars,config}Boris Kolpackov1-22/+22
We are going to use cc.config for something else.
2016-08-12Add support for ordering modules in config.buildBoris Kolpackov1-0/+4
2016-08-12Implement c/cxx toolchain cross-hintingBoris Kolpackov1-1/+2
2016-08-12Implement support for C compilationBoris Kolpackov1-0/+321
We now have two new modules: cc (c-common) and c.