aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/cc/common.cxx
AgeCommit message (Collapse)AuthorFilesLines
2020-07-01Add *.export.imp_libs to get rid of dual *.export.libs semanticsBoris Kolpackov1-36/+35
2020-06-26Minor terminology fix in commentsBoris Kolpackov1-3/+2
2020-06-26Fix race in library metadata protocolBoris Kolpackov1-2/+3
Specifically, we need to check whether the prerequisite_member is ad hoc before checking whether it is NULL because ad hoc ones are blanked out (set to NULL) during execute.
2020-05-22Make template definition available in all translation units where usedBoris Kolpackov1-27/+0
We were trying to be clever but GCC 10's IPA-SRA optimization didn't like it.
2020-04-30Rename target::member to target::adhoc_memberBoris Kolpackov1-1/+1
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-14/+2
Specifically, now config.<tool> (like config.cli) is handled by the import machinery (it is like a shorter alias for config.import.<tool>.<tool>.exe that we already had). And the cli module now uses that instead of custom logic. This also adds support for uniform tool metadata extraction that is handled by the import machinery. As a result, a tool that follows the "build2 way" can be imported with metadata by the buildfile and/or corresponding module without any tool-specific code or brittleness associated with parsing --version or similar outputs. See the cli tool/module for details. Finally, two new flavors of the import directive are now supported: import! triggers immediate importation skipping any rule-specific logic while import? is optional import (analogous to using?). Note that optional import is always immediate. There is also the import-specific metadata attribute which can be specified for these two import flavors in order to trigger metadata importation. For example: import? [metadata] cli = cli%exe{cli} if ($cli != [null]) info "cli version $($cli:cli.version)"
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-02-04Add note to manual on specifying search paths in compiler modeBoris Kolpackov1-0/+2
2020-02-03Add header/library search paths from compiler mode to sys_*_dirsBoris Kolpackov1-50/+16
2020-01-31Propagate installed library out (tag) when converting to nameBoris Kolpackov1-8/+18
2020-01-31Tag installed library targets with linker pathBoris Kolpackov1-20/+29
This makes sure we get different targets for different toolchains.
2019-11-29Reorder {cc,c/cxx}.{poptions,loptions}Boris Kolpackov1-4/+5
Now it is c/cxx first followed by cc which is the reverse order of coptions since the header/library search paths are examined in the order specified (in contrast to the "last value wins" semantics that we assume for coptions).
2019-11-07Don't add $install.lib to module library search path if import.build2 is NULLBoris Kolpackov1-6/+21
2019-11-05Add support for automatic importing of libbuild2 of installed caseBoris Kolpackov1-1/+16
2019-10-08Extend /LIBPATH handling to win32-msvc target systemBoris Kolpackov1-1/+3
2019-10-01Adapt to renaming butl::casecmp() to icasecmp()Karen Arutyunov1-1/+1
2019-08-28Move cc build system module to separate libraryKaren Arutyunov1-0/+1031