aboutsummaryrefslogtreecommitdiff
path: root/build2/c
AgeCommit message (Collapse)AuthorFilesLines
2017-02-13Add model mutex, make var_pool const by defaultBoris Kolpackov1-13/+13
2017-01-23Add bunch of missing const'sBoris Kolpackov1-2/+2
2017-01-06Store platform targets as typed target_tripletBoris Kolpackov1-5/+4
2017-01-05Update copyright yearBoris Kolpackov3-3/+3
2016-11-18Make names and vector<name> different types, add typed value constructorBoris Kolpackov1-4/+4
2016-09-05Handle /usr/local brain-deathBoris Kolpackov1-0/+2
2016-08-30Add support for target visibility, use for dist, test, installBoris Kolpackov1-1/+1
This means we can no longer write: install = false Now it should be: *: install = false
2016-08-28Limit c.std, cxx.std, and extension visibility to projectBoris Kolpackov1-1/+1
2016-08-27Reimplement UNIX rpath using process_library(), -rpath-link is still brokenBoris Kolpackov1-0/+1
2016-08-27Clean up library export, make c and cxx modules project root onlyBoris Kolpackov1-131/+143
So now c and cxx modules can only be loaded in project root scope (normally root.build). Also, the c.std and cxx.std must now be set *before* loading the module to take effect. This means we won't be able to handle old buildfiles anymore but old versions of build2 should be able to handle new *.std placement.
2016-08-26Add pkg-config support for import installedBoris Kolpackov1-0/+2
Redesign library importing/exporting while at it.
2016-08-24Pick *.libs variable depending on library type during static linkingBoris Kolpackov1-0/+2
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-23Rename cc.{vars,config} modules to cc.core.{vars,config}Boris Kolpackov1-3/+3
We are going to use cc.config for something else.
2016-08-22Cache process_path, use fallback search directory for binutilsBoris Kolpackov1-10/+11
2016-08-19Implement uninstall operationBoris Kolpackov1-0/+1
2016-08-12Implement support for C compilationBoris Kolpackov3-0/+299
We now have two new modules: cc (c-common) and c.