aboutsummaryrefslogtreecommitdiff
path: root/build2/cc/msvc.cxx
AgeCommit message (Collapse)AuthorFilesLines
2018-05-19Update copyright yearKaren Arutyunov1-1/+1
2018-01-08Implement compiler_info cachingBoris Kolpackov1-2/+2
2018-01-08Complete runtime/stdlib detectionBoris Kolpackov1-1/+5
2017-12-16Improve process execution diagnostics by reusing run_*() APIBoris Kolpackov1-1/+4
2017-12-09Fix git commit id calculationBoris Kolpackov1-1/+1
2017-10-03Extract system header search paths from GCC or compatibleBoris Kolpackov1-0/+19
2017-07-29Fix bug in installed import library search on WindowsBoris Kolpackov1-2/+3
2017-07-27Fix to print to diagnostics stream instead of std::cerrKaren Arutyunov1-4/+2
2017-06-12Remove few unused lambda capturesBoris Kolpackov1-2/+2
2017-05-01Add hxx extension for headersKaren Arutyunov1-10/+10
2017-03-02Implement parallel matchBoris Kolpackov1-40/+35
2017-02-13Use target:as<> instead of static_cast for target castingBoris Kolpackov1-3/+3
2017-02-13Tighten code that operates during both search/match and executeBoris Kolpackov1-11/+29
2017-02-13Pass const target& to recipesBoris Kolpackov1-1/+1
2017-01-19Get rid of extension_poolBoris Kolpackov1-7/+6
2017-01-05Update copyright yearBoris Kolpackov1-1/+1
2016-11-04Adopt to auto_fd introduced to libbutl fdstreams and processKaren Arutyunov1-1/+2
2016-09-15Add io_error alias for std::ios_base::failureKaren Arutyunov1-1/+1
2016-08-28Factor library search/processing out to cc::commonBoris Kolpackov1-5/+5
2016-08-27Clean up library export, make c and cxx modules project root onlyBoris Kolpackov1-3/+6
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-1/+0
Redesign library importing/exporting while at it.
2016-08-24Handle *.export.libs, distinguish interface and implementation dependenciesBoris Kolpackov1-9/+13
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-22Cache process_path, use fallback search directory for binutilsBoris Kolpackov1-8/+8
2016-08-12Implement support for C compilationBoris Kolpackov1-0/+342
We now have two new modules: cc (c-common) and c.