| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/5f31944b8942818aaf53571c76f5c6a9a9dafc72: Custom module map for j2objc_library
Automated g4 rollback of commit e7fe50aa727df9ef0a3d37fa258d017971035515.
*** Reason for rollback ***
Roll forward. The bzl change is removed because it has to be submitted after next Blaze release.
*** Original change description ***
Automated g4 rollback of commit 5f31944b8942818aaf53571c76f5c6a9a9dafc72.
*** Reason for rollback ***
This caused some build breaks.
*** Original change description ***
Custom module map for j2objc_library
PiperOrigin-RevId: 154726197
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This caused some build breaks.
*** Original change description ***
Custom module map for j2objc_library
PiperOrigin-RevId: 154608761
|
|
|
|
| |
PiperOrigin-RevId: 154606005
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 149110466
MOS_MIGRATED_REVID=149110466
|
|
|
|
|
|
|
|
|
| |
inputs/outputs in j2objc_library behind flag --experimental_j2objc_annotation_processing
Also added flag --experimental_zip_tree_artifact to switch on and off the zipping implementation of tree artifact generation.
--
MOS_MIGRATED_REVID=128586669
|
|
|
|
|
|
|
|
|
| |
When a file changes its execution root (for example, a previously checked in
file now becoming a generated file), the cache key would be the same, using
a broken module map.
--
MOS_MIGRATED_REVID=120703120
|
|
|
|
|
|
|
|
| |
Consists of adding @Immutable annotations, adding final modifiers, and changing
the types of fields to immutable types.
--
MOS_MIGRATED_REVID=120221067
|
|
|
|
|
|
|
| |
directly to newDeterministicWriter.
--
MOS_MIGRATED_REVID=115626619
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, module maps contain both "use <module>" entries that specify which
modules the current module map depends on, and "extern module" entries that
provide paths where to load the dependent module maps from.
This change adds a feature "module_map_without_extern_module", which instructs
blaze to not write the "extern module" entries into the module map. Instead,
the crosstool needs to add -fmodule-file flags for each dependent module file
where needed for the compile via the new build variable
"dependent_module_map_files".
Note that the feature is phrased negatively ("_without_") in order to simplify
the roll-out of this feature: as long as crosstools do not specify any
features, they still want the old behavior.
We cannot make the feature positive and add it to the legacy configuration, as
we currently cannot remove features that have already been set in the crosstool
file.
--
MOS_MIGRATED_REVID=104757413
|
|
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=89149156
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to keep the existing behavior when turning on C++ modules. The problem is that
a #include of a header gets internally translated into an import of the
header's (sub)module. Now, if all headers of a cc_library are in the same
module, this means, a single import of one of them makes the symbols of all of
them accessible. While this isn't inherently problematic, it breaks the
similarity between a modules and non-modules build.
This behavior is hidden behind a feature for now as I have just committed
necessary changes to Clang, which will need to be release to stable, before we
can flip everything.
Also, don't put a header as both normal and private header if it is present in both. (Or don't output two submodules with the new implementation).
--
MOS_MIGRATED_REVID=88723759
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
It was missing multiple members in its key computation.
RELNOTES: Fix .cppmap file re-generation.
--
MOS_MIGRATED_REVID=86074231
|
|
--
MOE_MIGRATED_REVID=85702957
|