| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120325869
|
|
|
|
| |
Change-Id: Id46910de46264b5824793ba75439c31ae331718f
|
|
|
|
|
|
|
| |
--
Change-Id: I5377f694bd6dc426d41feef75cd35145c3b47c2f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3450/
MOS_MIGRATED_REVID=120323262
|
|
|
|
|
|
|
| |
This is apparently unused.
--
MOS_MIGRATED_REVID=120317405
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for retrieving
the default values of options.
The field defaultMultipleValue was introduced in commit 51a491b89a9cd5f15c9a093a5693bc37e696e6e1 to allow defining a
default value for options that set allowMultiple. However due to the limitations of
the optionsParser end up being not useful since we cannot guarantee that an option
that allows multiple has a converter that returns a list of values.
Thus this CL deletes code that may confuse even more and clarifies the mechanism
that the options currently use to obtain their default values.
--
MOS_MIGRATED_REVID=120317261
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120315714
|
|
|
|
|
|
|
| |
As noticed in #1122.
--
MOS_MIGRATED_REVID=120315240
|
|
|
|
|
|
|
| |
Fixes #1156.
--
MOS_MIGRATED_REVID=120312138
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120309611
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120282869
|
|
|
|
|
|
|
| |
attribute based on the Rule itself (the transition may thus be determined based on the values of other attributes of the rule)
--
MOS_MIGRATED_REVID=120275649
|
|
|
|
|
|
|
|
|
|
|
| |
Adding AndroidDataSerializer, the serialize_format proto, and KeyValueConsumers (utility class for keeping consumers straight).
The serializtion is a bit more manual as previous experience has proven to me that simply writing all the resources into a proto map and pulling them out is not performant in the least. So, the serializer stores each message independent, the keys and then the values allowing for potential lazy loading and other optimizations in the future.
Also adds tests for parsing and writing style resources.
--
MOS_MIGRATED_REVID=120274904
|
|
|
|
|
|
|
| |
BuildConfiguration that is not the current rule context's configuration.
--
MOS_MIGRATED_REVID=120271518
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This prevents an ugly warning when you do something like:
new_local_repository(
name = "bazel_tools",
path = ".",
build_file = "BUILD",
)
--
MOS_MIGRATED_REVID=120271366
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120262286
|
|
|
|
|
|
|
|
|
| |
Now we only need to specify --cpu=x64_windows_msvc when using msvc toolchain
--
Change-Id: Id501dd9ef2fd6553285677605ec75e80499b9ef7
Reviewed-on: https://bazel-review.googlesource.com/#/c/3441
MOS_MIGRATED_REVID=120260588
|
|
|
|
|
|
|
|
|
|
|
| |
This avoids problems when some of the universe doesn't build, and should
make the IDE setup script a bit faster. Also use --keep_going in query
so that any future breakages don't break IDE setup.
--
Change-Id: If9bf30ca5d63f9d9a3455cbbb78b7139a3e5324d
Reviewed-on: https://bazel-review.googlesource.com/3430
MOS_MIGRATED_REVID=120250626
|
|
|
|
|
|
|
|
|
|
|
|
| |
With remote repositories, it is useful to do this to execute an input
file which isn't actually part of the source tree.
Closes #984
--
Change-Id: Ic986ea9bbe88e0edb933939ce1d7a8b6ea9d6e88
Reviewed-on: https://bazel-review.googlesource.com/#/c/3030/
MOS_MIGRATED_REVID=120248102
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
getTransitiveCompilationPrerequisites. The missing 'transitive' in the name is
misleading.
This change is a preparation for further refactorings that will in the end
introduce a getCompilationPrerequisites method that actually returns the
compilation prerequisites for a rule - as that will be require some more things
to be shuffled around in CppCompilationContext, this change gets the purely
syntactical change in first.
--
MOS_MIGRATED_REVID=120247461
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120247206
|
|
|
|
|
|
|
|
|
| |
It's wrong to assume it points to an absolute path.
Discovered in issue #1152.
--
MOS_MIGRATED_REVID=120242469
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120241405
|
|
|
|
|
|
|
| |
when in gRPC mode.
--
MOS_MIGRATED_REVID=120233121
|
|
|
|
|
|
|
| |
--
Change-Id: I4df7be7de77dd5d44b2090311bce79dbc85a6775
Reviewed-on: https://bazel-review.googlesource.com/#/c/3388
MOS_MIGRATED_REVID=120232900
|
|
|
|
|
|
|
| |
Fixes #1066.
--
MOS_MIGRATED_REVID=120232176
|
|
|
|
|
|
|
| |
--
Change-Id: I6a2f9026fda578905ccb72b317223eaca16b882b
Reviewed-on: https://bazel-review.googlesource.com/#/c/3440
MOS_MIGRATED_REVID=120228541
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also sets the Bazel workspace name to io_bazel_source.
Fixes #848.
Relevant to #1116, #1124,
RELNOTES[INC]: All repositories are now directly under the x.runfiles directory in the runfiles tree (previously, external repositories were at x.runfiles/main-repo/external/other-repo. This simplifies handling remote repository runfiles considerably, but will break existing references to external repository runfiles.
---
Furthermore, if a Bazel project does not provide a workspace name in the WORKSPACE file, Bazel will now default to using __main__ as the workspace name (instead of "", as previously). The repository's runfiles will appear under x.runfiles/__main__/.
--
MOS_MIGRATED_REVID=120224534
|
|
|
|
|
|
|
| |
Fixes #1122.
--
MOS_MIGRATED_REVID=120223970
|
|
|
|
|
|
|
|
|
| |
packages not in third_party. We don't need to police users' external repositories.
Fixes #1151
--
MOS_MIGRATED_REVID=120222222
|
|
|
|
|
|
|
|
| |
Consists of adding @Immutable annotations, adding final modifiers, and changing
the types of fields to immutable types.
--
MOS_MIGRATED_REVID=120221067
|
|
|
|
|
|
|
| |
requirements. Uses this mechanism to configure c/c++ compilation and linking for darwin execution from the crosstool.
--
MOS_MIGRATED_REVID=120218079
|
|
|
|
|
|
|
| |
Fixes #760.
--
MOS_MIGRATED_REVID=120217217
|
|
|
|
|
|
|
|
|
|
| |
Second pass.
Consists of adding @Immutable annotations, adding final modifiers, and changing
the types of fields to immutable types.
--
MOS_MIGRATED_REVID=120216592
|
|
|
|
|
|
|
| |
Its old name was confusing because resolve() and getDefault() do radically different things: getDefault() returns a good enough lie for when BuildConfiguration is not available, and resolve() resolves the dependency when we do have a BuildConfiguration.
--
MOS_MIGRATED_REVID=120212630
|
|
|
|
|
|
|
|
|
|
|
|
| |
cc_configure assumed the paths returned by $(CC) -E -xc++ -v
where not containing any extra information but clang on OS X
adds " (framework directory)" for path from Frameworks. This
change strip this out.
--
Change-Id: I90617e825100f86a1f0991e128755802da2c7afd
Reviewed-on: https://bazel-review.googlesource.com/3389
MOS_MIGRATED_REVID=120210800
|
|
|
|
|
|
|
| |
Work towards #930.
--
MOS_MIGRATED_REVID=120205147
|
|
|
|
|
|
|
|
|
|
|
|
| |
The version command is not expected to every run any actions.
Hence any messages about progress of the build process or running
actions would be confusing. Therefore, signal this fact to allow
the experimental UI to present information accordingly.
--
Change-Id: I8a75704a39e161f52c4d008677f62e4b36097647
Reviewed-on: https://bazel-review.googlesource.com/#/c/3387
MOS_MIGRATED_REVID=120203058
|
|
|
|
|
|
|
|
|
|
|
| |
Drive-by fix: eliminate the GRPC messages from the console by passing a null logging function.
This also prepares us for the time when multiple commands will be running, because then we'll need to tell which command exactly we want to interrupt.
Work towards #930.
--
MOS_MIGRATED_REVID=120203008
|
|
|
|
|
|
|
| |
Work towards #930. With this, it's conceivable that server mode works on Windows to some degree (I haven't tried, though, because there are many issues that need to be fixed)
--
MOS_MIGRATED_REVID=120202037
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
looks like this is probably break []
*** Original change description ***
Bind path to xcrunwrapper in workspace files.
--
MOS_MIGRATED_REVID=120167193
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change disables --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top, and finishes replacing them with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}.
RELNOTES: Replace --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}
--
MOS_MIGRATED_REVID=120154954
|
|
|
|
|
|
|
|
|
| |
If no AndroidSdkProvider is present, JackAspect exits with an error
instead of throwing and thus crashing Bazel. This is acceptable; the
Android rules which JackAspect is attached to will do the same.
--
MOS_MIGRATED_REVID=120150996
|
|
|
|
|
|
|
| |
--
Change-Id: Ie4236fbadc63ef38f08783acc0162cf0dd4fe872
Reviewed-on: https://bazel-review.googlesource.com/3422
MOS_MIGRATED_REVID=120146252
|
|
|
|
|
|
|
| |
For consistency with java_library.javacopts and the top-level --javacopts flag.
--
MOS_MIGRATED_REVID=120145920
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120145833
|
|
|
|
|
|
|
| |
target. We also no longer say that the target will not be built because it may well happen during a query, when no building is happening anyway.
--
MOS_MIGRATED_REVID=120130554
|
|
|
|
|
|
|
| |
options classes.
--
MOS_MIGRATED_REVID=120125572
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120124909
|
|
|
|
|
|
|
|
| |
builds with C++ modules as modules can be built without waiting on dependencies
that are only required for the module's implementation.
--
MOS_MIGRATED_REVID=120119435
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120117310
|