aboutsummaryrefslogtreecommitdiff
path: root/build2/cc/compile.cxx
AgeCommit message (Collapse)AuthorFilesLines
2016-09-15Add io_error alias for std::ios_base::failureKaren Arutyunov1-3/+3
2016-09-06Ignore instead of overriding header prefix (now more specific -I's come first)Boris Kolpackov1-8/+10
2016-09-05Change order in which library options are processedBoris Kolpackov1-11/+11
The idea is that we want more "specialized" -I/-L options before more "generic" in order to make sure we don't pick up installed headers or libraries. This is still not bullet-proof though.
2016-09-05Handle /usr/local brain-deathBoris Kolpackov1-0/+23
2016-09-04Adjust to freebsd to bsd target class changeBoris Kolpackov1-3/+3
2016-09-04Fix initializer list lifetime issuesBoris Kolpackov1-6/+2
2016-08-28Optimize library processingBoris Kolpackov1-87/+89
2016-08-28Factor library search/processing out to cc::commonBoris Kolpackov1-13/+12
2016-08-28Extract pkg-config information for both static/shared at onceBoris Kolpackov1-21/+22
We also no longer pick shared/static file rather entering them as "our" lib{} target. This way we use the link order of the importer "transitively".
2016-08-27Fix rpath-linkBoris Kolpackov1-3/+6
2016-08-27Clean up library export, make c and cxx modules project root onlyBoris Kolpackov1-11/+13
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-31/+77
Redesign library importing/exporting while at it.
2016-08-24Handle *.export.libs, distinguish interface and implementation dependenciesBoris Kolpackov1-2/+2
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-23Handle "prefixless" include directory to project mapping betterBoris Kolpackov1-72/+119
2016-08-22Cache process_path, use fallback search directory for binutilsBoris Kolpackov1-5/+9
2016-08-13Use extension derivation function rather than extension variable directlyBoris Kolpackov1-5/+10
2016-08-12Implement support for C compilationBoris Kolpackov1-0/+1480
We now have two new modules: cc (c-common) and c.