| Commit message (Collapse) | Author | Age |
|
|
|
| |
Change-Id: I99487b78a4f9a564c0618209f638425e2e39baa6
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112409554
|
|
|
|
|
|
|
|
|
|
|
| |
With latest change to the bootstrap compilation, some options
were wrongly moved around.
Tested with `source scripts/ci/build.sh; bazel_build` for JAVA_VERSION
1.7 and 1.8.
--
MOS_MIGRATED_REVID=112409496
|
|
|
|
|
|
|
|
|
|
| |
This method was used only twice. Now there is only one entry point for requesting
a rule in the external package (RepositoryFunction#getRule(String, Environment)).
This is a step towards supporting loading skylark rules in the workspace file from
remote repository.
--
MOS_MIGRATED_REVID=112407797
|
|
|
|
|
|
|
| |
This remove all C++ compilation in bootstrapping itself.
--
MOS_MIGRATED_REVID=112407516
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112404257
|
|
|
|
|
|
|
| |
Another step towards no C++ compilation outside of Bazel for bootstrapping.
--
MOS_MIGRATED_REVID=112399835
|
|
|
|
|
|
|
|
| |
process-wrapper is a C++ tool, replacing by a dummy shell version to
reduce the number of C++ compiler calls during the bootstrap process.
--
MOS_MIGRATED_REVID=112398152
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112397181
|
|
|
|
|
|
|
| |
This method is used only once now so inline.
--
MOS_MIGRATED_REVID=112396086
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112394770
|
|
|
|
|
|
|
|
| |
This simplify the bootstrap process and remove a C++ tool from
the bootstrap binary.
--
MOS_MIGRATED_REVID=112394555
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112394431
|
|
|
|
|
|
|
| |
deprecated.
--
MOS_MIGRATED_REVID=112392227
|
|
|
|
|
|
|
|
|
| |
to do such a load will result in a skyframe circular dependency exception.
As a side effect of this change, SkylarkImportFailedExceptions thrown by SkylarkImportLookupFunction are now caught by PackageFunction and wrapped and rethrown as a PackageFunctionException. Previously, the first exception wasn't caught, generating an uncaught exception error at top level.
--
MOS_MIGRATED_REVID=112328755
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112290581
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112285296
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112284252
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112280234
|
|
|
|
|
|
|
| |
See http://ci.bazel.io/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=darwin-x86_64/302/console
--
MOS_MIGRATED_REVID=112280018
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112273574
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note: This specification currently does not have any effect, but soon...
In the default mode, when an aspect does not call any of the configuration
fragment methods on its AspectDefinition.Builder, the old behavior will
persist; aspects can only access fragments their associated rule has access
to, and have no guarantee as to what those fragments are.
This mode will become deprecated with a future CL.
If an aspect does call a configuration fragment method, it will have a
configuration fragment policy. In a future CL, this will mean it will be
restricted to accessing only those fragments, but will be understood as
requiring access to them for the purposes of dynamic configuration, even if
the rule it is attached to or created by does not otherwise require them.
Eventually, all aspects will be required to declare their configuration
fragments this way.
Skylark aspects may also declare configuration fragments as of this CL.
Two new parameters are added to the aspect() function, fragments and
host_fragments, mirroring the similar parameters for rules.
If both of these parameters are empty or unspecified, the default mode
is used, as with normal aspects.
Also in this CL:
* Minor javadoc fixes for AspectDefinition.
* Additional tests for AspectDefinition.
--
MOS_MIGRATED_REVID=112271713
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112267385
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112267123
|
|
|
|
|
|
|
| |
Fixes #637
--
MOS_MIGRATED_REVID=112261246
|
|
|
|
|
|
|
|
|
| |
host crosstool.
RELNOTES[NEW]: --grte_top no longer also sets --host_grte_top in the absence of the latter
--
MOS_MIGRATED_REVID=112258796
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rule.
Add native.rules(), which returns all previously defined rules.
These primitives can be used to write Skylark extensions that aggregate over the contents of a BUILD file, eg.
def instantiate_if_needed(name):
n = name + "_wrapped"
if not native.rule(n):
py_test(name = n , ... )
def archive_cc_src_files(tag):
all_src = []
for r in native.rules().values():
if tag in r["tags"] and r["kind"] == "cc_library":
all_src.append(r["srcs"])
native.genrule(cmd = "zip $@ $^", srcs = all_src, outs = ["out.zip"])
RELNOTES: Support aggregation over existing rules in Skylark extensions
through native.rules and native.rule.
--
MOS_MIGRATED_REVID=112249050
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112248853
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is in preparation for moving the output dumping to the Reporter for
two reasons:
- we're currently relying on there being a Reporter which locks on itself;
i.e., this code is tightly coupled with the Reporter code
- the current Blaze output is confusing; we first print an info event, then
the actual output, and then an error event - putting the Reporter in control
allows us to fix that
--
MOS_MIGRATED_REVID=112240684
|
|
|
|
|
|
|
|
|
| |
Instead use the current tools from the repository. This
simplifies the bootstrap binary and is a step towards
no C++ compilation for the bootstrap binary.
--
MOS_MIGRATED_REVID=112240524
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112239696
|
|
|
|
|
|
|
| |
See http://ci.bazel.io/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=linux-x86_64/301/console
--
MOS_MIGRATED_REVID=112238153
|
|
|
|
|
|
|
|
| |
This method is exposed to Skylark and will enable correct handling of protobuf skylark files.
See #784
--
MOS_MIGRATED_REVID=112235357
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112231484
|
|
|
|
|
|
|
|
|
| |
The iOS provisioning profile should be local to the developer / company.
Fixes #780.
--
MOS_MIGRATED_REVID=112229161
|
|
|
|
|
|
|
|
|
| |
Fixes #769.
--
Change-Id: I085b0a9c9faed45bee8cf4185a71531b95a66e14
Reviewed-on: https://github.com/bazelbuild/bazel/pull/779
MOS_MIGRATED_REVID=112228906
|
|
|
|
|
|
|
|
|
|
|
| |
build flags to clang based on a specified mode.
This handles the very basic case of objc_* rule compilation which does not depend on non-objc targets. Until we support passing bitcode flags
for cc compilation, such builds will be broken if bitcode is enabled (one may be able to get around this by propagating the appropriate bitcode flag to --copt, but we'll want to do this as part of the apple_bitcode flag). Additionally, we will want to use apple_bitcode to pass bitcode-enabling
properties to generated xcode projects.
--
MOS_MIGRATED_REVID=112192290
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In preparation for allowing aspects to have their own configuration fragments
specified, allow ConfigurationFragmentPolicy.Builder to merge with built policies
more easily, setting up SetMultimaps in place of maps of sets. This changes how
named (Skylark) fragments are declared in the RuleContext builder, hopefully to
be a bit easier to write.
In order to do this, make SkylarkModuleNameResolver the only name resolver in use
(because it is the only name resolver which exists) so as to not worry about
collisions of different name resolvers.
This also changes isLegalConfigurationFragment's one-argument form to mean
"legal in ANY configuration" rather than "legal in the target (NONE)
configuration", as that is how it's used by TransitiveTargetFunction. Uses of it to
mean the latter have been revised to be more explicit.
Also in this CL:
* refactor ConfigurationFragmentPolicy to enforce its contracts about which
ConfigurationTransitions are legal
* use containsEntry or containsValue rather than looking in get(key) or values()
for the configuration fragment multimaps
* add tests for ConfigurationFragmentPolicy
* make SkylarkModuleNameResolver a static method
--
MOS_MIGRATED_REVID=112191439
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, for some types of errors, you'd just see "WORKSPACE file
could not be parsed" if there was a syntax error (instead of what the
syntax error was).
Change-Id: Ia278cf23b79f8daba02917cdfb4cc515a87080b1
--
Change-Id: Ia278cf23b79f8daba02917cdfb4cc515a87080b1
Reviewed-on: https://github.com/bazelbuild/bazel/pull/774
MOS_MIGRATED_REVID=112190322
|
|
|
|
|
|
|
|
|
| |
They are not in third_party directory, so they should start with BAZEL.
--
Change-Id: I68b561ef8d06f50e8223af432a4f8aceb1a9c09d
Reviewed-on: https://bazel-review.googlesource.com/#/c/2670/
MOS_MIGRATED_REVID=112173485
|
|
|
|
|
|
|
| |
This is a prerequisite to making some changes to PackageFunction that require handling another exception.
--
MOS_MIGRATED_REVID=112172100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
just warn if a target turns out to not be present. This means that queries may return unexpected results. For instance, if "query" means "bazel query --order_output=no ", then here are the results of two queries:
query --universe_scope=//foo/... //foo:output_file
//foo:output_file
query --universe_scope=//foo/... deps(//foo:output_file)
WARNING: Targets not in graph [//foo:output_file generated_file]
//foo:output_file
--
MOS_MIGRATED_REVID=112163475
|
|
|
|
|
|
|
| |
some recent profiling.
--
MOS_MIGRATED_REVID=112161558
|
|
|
|
|
|
|
| |
targeting Apple platforms.
--
MOS_MIGRATED_REVID=112152418
|
|
|
|
|
|
|
| |
environments of runtime tools.
--
MOS_MIGRATED_REVID=112149571
|
|
|
|
|
|
|
|
|
|
|
| |
statements work in remote repositories.
This work is somewhat sisyphean; the principled thing to do would be to just do this resolution when labels are parsed.
Fixes #783.
--
MOS_MIGRATED_REVID=112137996
|
|
|
|
|
|
|
| |
the tests (which spawn multiple tests in the outside Bazel instance with each its own inner Bazel instance which in turn have their own thread pool) doesn't grind the machine to a halt.
--
MOS_MIGRATED_REVID=112132298
|
|
|
|
|
|
|
|
|
| |
Using java8-jdk will match both openjdk-8-jdk and oracle-java8-jdk similarly with java7-jdk. If
either of them are installed on the system allowing bazel to be installed in either case. Also the jdk source is not needed to create the bazel deb pacakge.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/785
MOS_MIGRATED_REVID=112132285
|
|
|
|
|
|
|
| |
It isn't necessary anymore.
--
MOS_MIGRATED_REVID=112132272
|
|
|
|
|
|
|
|
| |
See https://groups.google.com/forum/#!topic/bazel-discuss/xPe-oaqWZ6s
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/787
MOS_MIGRATED_REVID=112129205
|