| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
decompresses tarballs.
Issue link: https://github.com/bazelbuild/bazel/issues/574
--
MOS_MIGRATED_REVID=132434278
|
|
|
|
|
|
|
| |
generating the directory tree nodes efficiently.
--
MOS_MIGRATED_REVID=132433991
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132433369
|
|
|
|
|
|
|
|
|
| |
There doesn't seem to be any need for a C++ toolchain to create a Python config
anymore. I looked through the change history, but didn't find any obvious
culprits / reasons for the current code.
--
MOS_MIGRATED_REVID=132429818
|
|
|
|
|
|
|
| |
experimental_objc_library.
--
MOS_MIGRATED_REVID=132429745
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132423268
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES[INC]: repository_ctx.{download,download_and_extract,execute} API now use
named parameters for optional parameters and no longer uses argument
type to distinguished between arguments (executable attribute name
must be specified when preceding optional arguments are missing).
Fixes #1426.
--
Change-Id: I41d174cd9fd5c47edf4e2e9a86ce7f6c7882a104
Reviewed-on: https://bazel-review.googlesource.com/#/c/5673
MOS_MIGRATED_REVID=132421955
|
|
|
|
|
|
|
|
|
| |
Move more logic from FilesFileOperationsTest into
WindowsTestUtil, and further separate test files
in the BUILD file.
--
MOS_MIGRATED_REVID=132417714
|
|
|
|
|
|
|
| |
external/bazel_tools/tools/cpp/osx_cc_wrapper.sh: No such file or directory"
--
MOS_MIGRATED_REVID=132415409
|
|
|
|
|
|
|
|
| |
build first before discovering their inputs and this build doesn't properly
declare its inputs if we do pruning.
--
MOS_MIGRATED_REVID=132414200
|
|
|
|
|
|
|
| |
RELNOTES[INC]: filegroup-based C++ toolchains are not supported anymore. --*_crosstool_top options must always point to a cc_toolchain_suite rule (or an alias of one).
--
MOS_MIGRATED_REVID=132410829
|
|
|
|
|
|
|
|
|
|
|
|
| |
Additionally:
- clean up the corresponding BUILD file a bit
- add a comment to Path
A subsequent change will add tests for
WindowsFileSystem, then fix a bug there.
--
MOS_MIGRATED_REVID=132408212
|
|
|
|
|
|
|
| |
experimental_auto_top_level_union_objc_protos flag.
--
MOS_MIGRATED_REVID=132395070
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132358544
|
|
|
|
|
|
|
| |
RELNOTES: swift_library can be used to build watchOS apps.
--
MOS_MIGRATED_REVID=132355955
|
|
|
|
|
|
|
| |
include paths.
--
MOS_MIGRATED_REVID=132345416
|
|
|
|
|
|
|
|
|
| |
filegroup to declare C++ toolchains.
Tested by actually removing support for filegroups; it's a ~5-line change, but it's better to do that separately so that it can be rolled back easily if need be.
--
MOS_MIGRATED_REVID=132320198
|
|
|
|
|
|
|
|
|
| |
string that points to a remote repository.
Fixes #1442.
--
MOS_MIGRATED_REVID=132320130
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is so that the repository name can be included in the root.
To avoid breaking Bazel's CI which tests the HEAD code against the latest
release, none of the Skylark rules in Bazel can be updated to use
ctx.{bin,genfiles}_dir yet, we will have to wait for the 0.3.2 release to
actually update the call sites. However, this change is to effectively
deprecate ctx.configuration.{bin,genfiles}_dir: it undocuments them and I will
announce the change on the list.
RELNOTES[INC]: bin_dir and genfiles_dir are now properties of ctx, not
configuration. That is, to access the bin or genfiles directory from a
Skylark rule, use ctx.bin_dir or ctx.genfiles_dir (not
ctx.configuration.{bin,genfiles}_dir). At the moment, you can access
{bin,genfiles}_dir from either, but the ctx.configuration version will
stop working in a future release.
--
MOS_MIGRATED_REVID=132319900
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132317938
|
|
|
|
|
|
|
|
|
| |
Previously, it was possible for us to edit the options in command.editOptions,
after reporting them to the modules, though I don't have any examples of that
happening. I found this just looking through the code.
--
MOS_MIGRATED_REVID=132310873
|
|
|
|
|
|
|
|
|
| |
The functions were already available in Skylark extensions, but not directly in the BUILD files.
RELNOTES[NEW]: print and fail are now available in BUILD files.
--
MOS_MIGRATED_REVID=132307913
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132261111
|
|
|
|
|
|
|
|
|
|
| |
All usage of Guava has been removed from junitrunner. It is now safe to also remove
all deps from the BUILD files.
Fixing issue #1150.
--
MOS_MIGRATED_REVID=132252042
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Prunes .modulemap files incorrectly. See [].
*** Original change description ***
Implement input pruning using .d files in objc.
--
MOS_MIGRATED_REVID=132246906
|
|
|
|
|
|
|
|
|
| |
Fixes #1470.
--
Change-Id: If16e32ac6e9b71680b6ed73987f1164545a99920
Reviewed-on: https://bazel-review.googlesource.com/#/c/5670/
MOS_MIGRATED_REVID=132243744
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replaced late bound attributes with computed default attributes) with two bug fixes:
1. Unlike SkylarkComputedDefault, SkylarkComputedDefaultTemplate did not sort the names of its attribute dependencies. Consequently, lookup operations failed when callback functions in bzl files specified the names of their required attributes in a non-alphabetical order since the order of the key tuples was different (e.g. [1, 2] vs [2, 1]).
It would be less error prone to always sort the dependencies in createDependencyAssignmentTuple(), but this would impact performance.
2. SkylarkCallbackFunction ignores the legacy "cfg" parameter in callback functions. This special case should be deleted once all cfg parameters have been removed from the depot.
--
MOS_MIGRATED_REVID=132235927
|
|
|
|
|
|
|
| |
KillServerProcess() so that we don't call malloc() in signal handlers.
--
MOS_MIGRATED_REVID=132232499
|
|
|
|
|
|
|
| |
RELNOTES: Reverts a change that lead to misleading warnings.
--
MOS_MIGRATED_REVID=132230645
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132226460
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is now enabled by default, and this change removes the code path where
it's disabled.
Remove a few tests that were testing the removed code, and rewrite some others
that still seem useful. We still drop configured targets on configuration
changes, so we use that to check that things are dropped from Skyframe.
--
MOS_MIGRATED_REVID=132226208
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Any java rule that mixes generated and non-generated sources
will produce a filtered jar containing only the generated
output.
For a java rule with only "normal" sources or only generated
source files, no filtered jar is produced.
This will allow the IDE to resolve those generated sources.
RELNOTES:None
--
MOS_MIGRATED_REVID=132113568
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132097087
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132088164
|
|
|
|
|
|
|
|
| |
1. MinimumOSVersion should be for watchOS version, not iOS version. At some point we may want this specifiable to a different value, but, for now, this is set to the current watchOS SDK version.
2. WatchOS2 extension does not need UIRequiredDeviceCapabilities set, so this is removed.
--
MOS_MIGRATED_REVID=132085592
|
|
|
|
|
|
|
|
| |
Also, the watch2 extension rule (and future bundling rules which depend on apple_binary) now depend on the combined-arch library
of that apple_binary dependency, instead of re-lipoing the binaries themselves.
--
MOS_MIGRATED_REVID=132077913
|
|
|
|
|
|
|
| |
classes to be reusable for apple_static_library and apple_dynamic_library
--
MOS_MIGRATED_REVID=132066681
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132066368
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132061988
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132058819
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel users that are using a different Guava version than the one in the
junitrunner jar are getting an IncompatibleClassChangeError. Rewriting
parts of junitrunner code so it won't depend on Guava anymore.
Continuing progress on issue #1150.
--
MOS_MIGRATED_REVID=132054901
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132051338
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/1680
--
MOS_MIGRATED_REVID=132051176
|
|
|
|
|
|
|
|
| |
I'm going to refactor these args out to crosstool so I wrote this little test
to keep me honest.
--
MOS_MIGRATED_REVID=132044125
|
|
|
|
|
|
|
| |
WindowsFileSystem.java does not yet use it.
--
MOS_MIGRATED_REVID=132043739
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pruning here can lead to a insufficient rebuilds which in turn cause
module-out-of-date errors. The problem surfaces if a module A depends on a
module B, but the headers of module A don't actually use any of B's headers.
Then we would currently not need to rebuild A when B changes although we are
storing a dependency in it. If B changes and we then build something that uses
A (a header of it), we mark A as well as all of its transitive dependencies as
inputs. We still don't need to rebuild A, as none of its inputs have changed,
but we do rebuild B now and then the two modules are out of sync.
For now, just disable pruning of header modules while building the modules. In
the long run, it would be even better to not embed a dependency on B into A,
but that requires signficantly larger changes.
--
MOS_MIGRATED_REVID=132039754
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132039389
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=131995795
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=131990160
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=131986739
|