| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
Most current invocations of the ResourceSet constructor shouldn't
care about any new dimensions we add to restrict test execution. This
change allows us to make those changes, keep the ResourceSet ctor
symmetrical, and avoid contaminating those ctor call sites with noise.
--
MOS_MIGRATED_REVID=86826112
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=86797852
|
|
|
|
|
|
|
|
| |
Gets rid of a confusing warning that there are no object files, but something
is linked.
--
MOS_MIGRATED_REVID=86777258
|
|
|
|
|
|
|
|
| |
This can otherwise clash with C/C++ compiles where the source file has the same
name as the target.
--
MOS_MIGRATED_REVID=86776429
|
|
|
|
|
|
|
| |
dependencies just generate pic or non-pic header modules.
--
MOS_MIGRATED_REVID=86686907
|
|
|
|
|
|
|
| |
This required pulling the feature configuration into the rule-specific code.
--
MOS_MIGRATED_REVID=86685776
|
|
|
|
|
|
|
| |
The only slightly different thing here is that now, instead of using target.getConfiguration().isCodeCoverageEnabled() we use BuildRequest.Options.collectCodeCoverage, but the only place where this is not the same I can think of is InputFileCT, which does not have baseline coverage files anyway.
--
MOS_MIGRATED_REVID=86682774
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
configuration.
Together with [] (change to the crosstool configuration), the
resulting blaze is able to build header modules (minus clang bugs).
Detailed changes:
1. Adapt CppCompileAction to only insert the arguments itself if the crosstool
does not specify a feature.
2. Make CppCompileAction provide the build variables to the flag expansion.
3. Pass package features through to the new feature selection / crosstool
configuration; allow rules to always request features and mark features
as unsupported.
4. Add feature "header_module_includes_dependencies" that controls whether we
can only provide top-level header modules in the ${module_files} build
variable; the currently integrated clang does not fully support that yet.
5. Add feature "use_header_modules", which allows targets to use compiled
header modules without being compilable as module themselves.
6. Convert tests to use the feature configuration where it makes sense; we will
be able to delete a lot of unit tests once the control via the feature
configuration is rolled out to the stable crosstool, and implement them
as crosstool integration tests.
--
MOS_MIGRATED_REVID=86680884
|
|
|
|
|
|
|
|
|
|
| |
A cc_fake_binary needs all additional artifacts referenced in the compile
command line in its runfiles tree.
RELNOTES: Fix layering_check with cc_fake_binary.
--
MOS_MIGRATED_REVID=86596049
|
|
|
|
|
|
|
|
|
| |
It was missing multiple members in its key computation.
RELNOTES: Fix .cppmap file re-generation.
--
MOS_MIGRATED_REVID=86074231
|
|
|
|
|
|
|
| |
execPath), with a skyframe native implementation ArtifactFactory.resolveSourceArtifact(Iterable<PathFragment> execPaths, PackageRootResolver resolver).
--
MOS_MIGRATED_REVID=86062289
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=85970303
|
|
|
|
|
|
|
| |
configuration.
--
MOS_MIGRATED_REVID=85710366
|
|
--
MOE_MIGRATED_REVID=85702957
|