| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
environment variables to pass to actions
--
MOS_MIGRATED_REVID=111608329
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111537858
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111453115
|
|
|
|
|
|
|
|
|
| |
This commit adds proto messages that represent configurable values,
and modifies attribute value serialization code to handle those
values, which are called SelectorLists.
--
MOS_MIGRATED_REVID=111149272
|
|
|
|
|
|
|
| |
that Blaze can assign a default executable name, for when CFBundleExecutable is not given.
--
MOS_MIGRATED_REVID=110363400
|
|
|
|
|
|
|
|
|
| |
instead of multiple plists to merge and variable substitutions to apply.
The new key bundle_info_plist_file, gives the path to the completed plist. If it is defined, the keys source_plist_file and variable_substitution are not used.
--
MOS_MIGRATED_REVID=110010012
|
|
|
|
|
|
|
| |
the automatic entries from the other plist files to be merged.
--
MOS_MIGRATED_REVID=109998193
|
|
|
|
|
|
|
|
|
| |
to plmerge.
As of this change plmerge can consume either a protobuf or command line arguments. Once bazel uses plmerge strictly with protobufs, the command line arguments will be deprecated.
--
MOS_MIGRATED_REVID=109716003
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=109305952
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=109089224
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108985661
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108964575
|
|
|
|
|
|
|
|
|
| |
This boolean matches bazel's semantics on whether a R.java class should
be generated. Android Studio generates its own in-memory class, but we
need to know *whether* we should generate one.
--
MOS_MIGRATED_REVID=108175802
|
|
|
|
|
|
|
| |
so that they can cache and reuse state for unchanged inputs over multiple builds.
--
MOS_MIGRATED_REVID=107066408
|
|
|
|
|
|
|
| |
We will eventually want to put these in sets, and don't want to use slow reflection-based equals methods.
--
MOS_MIGRATED_REVID=107065999
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106588003
|
|
|
|
|
|
|
|
| |
The cost-benefit isn't there to pay a square cost to roll these up on
the blaze side. Android Studio has to do it on its end instead.
--
MOS_MIGRATED_REVID=105971068
|
|
|
|
|
|
|
|
| |
This supersedes bin/gen files on Android SDK. The fields are removed
entirely since the proto isn't public yet.
--
MOS_MIGRATED_REVID=105130701
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105054615
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add ide-resolve output group
* Add jars, ijars, source jars
* Add idl jars
* Add gen jars
* Add java_import inputs (in case they are generated)
* Add manifest inputs (in case they are generated)
* Rename ide-build -> ide-info (build is too ambiguous)
* Remove generated manifest
--
MOS_MIGRATED_REVID=104464380
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104331163
|
|
|
|
|
|
|
|
|
|
| |
This is the new conventions for Copyrights line and some were missed in the previous change.
Generated by:
find -type f -exec sed -i -E 's/Copyright 201([54]) Google Inc/Copyright 201\1 The Bazel Authors/' '{}' ';'
--
MOS_MIGRATED_REVID=104189975
|
|
|
|
|
|
|
| |
--invocation_policy startup flag and allows an application invoking Bazel to set or override flag values (whether from the command line or a bazelrc).
--
MOS_MIGRATED_REVID=104160290
|
|
|
|
|
|
|
|
|
|
| |
These outputs are a jar and source jar for the results of aidl processing.
This is used to add aidl output to IDEs separate from the source code,
similar to annotation output (gen jars).
--
MOS_MIGRATED_REVID=104024453
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
AndroidStudioInfoAspect.
--
MOS_MIGRATED_REVID=103635637
|
|
|
|
|
|
|
|
|
|
|
| |
arguments to OTHER_LDFLAGS. Command lines now use -l"name" to link libraries. This solves the problem that libraries in Xcode 7 now have .tbd files instead of dylibs in device builds and maintains backwards compatibility with Xcode 6.
Also modifies Bazel Objclink action to pass in libraries as -l"name" arguments.
RELNOTES:Adds support for dylibs on devices for Xcode 7.
--
MOS_MIGRATED_REVID=103589448
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103547846
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103089400
|
|
|
|
|
|
|
|
|
|
|
|
| |
They're not cheap to serialize or reconstitute and we don't really need them.
This does leave some odd ends around, in particular i decided to keep deserialization context around as i can picture use for it soon. Also return non-null values from all
of EmptyLocation's method since while the javadocs declare that LineAndColumn and Path
can be null, there does exist code which does not take this into account, this is for
another change.
--
MOS_MIGRATED_REVID=102758810
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102648848
|
|
|
|
|
|
|
| |
error.
--
MOS_MIGRATED_REVID=102582717
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102057837
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows to prevent expansion of flag sets based on whether build variables
are available. If required_variables is not set, and a variable that is
referenced in the flag_set's flags is not available, the build will fail.
We need the new behavior when some input files (for example profile data in
FDO enabled builds) are only available for a subset of the translation units of
a given target.
--
MOS_MIGRATED_REVID=100028996
|
|
|
|
|
|
|
| |
list type.
--
MOS_MIGRATED_REVID=100024899
|
|
|
|
|
|
|
| |
--
Change-Id: I8b896e6d4234b5a92d769a16cff70704f1fc9d40
Reviewed-on: https://bazel-review.googlesource.com/1700
MOS_MIGRATED_REVID=99176169
|
|
|
|
|
|
|
|
|
|
| |
Compare:
https://screenshot.googleplex.com/hzmgwbpUeuf
RELNOTES:Target names in Xcode projects have been simplified. This may require recreating any schemes that you have defined.
--
MOS_MIGRATED_REVID=98664733
|
|
|
|
|
|
|
|
|
|
|
|
| |
At this time, Skylark-defined rule classes don't get serialized, and
aren't available at package deserialization time. To allow packages
with Skylark-defined rule classes to deserialize, we provide a
placeholder rule class implementation for deserialized Skylark rules.
Resubmitting after previous rollback.
--
MOS_MIGRATED_REVID=97972209
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[]*** Reason for rollback ***
Large number of newly broken targets found by []
*** Original change description ***
Provide placeholder rule class for deserialized Skylark rules
At this time, Skylark-defined rule classes don't get serialized, and
aren't available at package deserialization time. To allow packages
with Skylark-defined rule classes to deserialize, we provide a
placeholder rule class implementation for deserialized Skylark rules.
--
MOS_MIGRATED_REVID=97716849
|
|
|
|
|
|
|
|
|
|
| |
At this time, Skylark-defined rule classes don't get serialized, and
aren't available at package deserialization time. To allow packages
with Skylark-defined rule classes to deserialize, we provide a
placeholder rule class implementation for deserialized Skylark rules.
--
MOS_MIGRATED_REVID=97679963
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=97675174
|
|
|
|
|
|
|
| |
passed from Bazel.
--
MOS_MIGRATED_REVID=96605573
|
|
|
|
|
|
|
|
|
|
|
|
| |
For each compilation unit, JavaBuilder will record:
-source path
-package name
-a list of top-level class names
-whether the file was generated by an annotation processor
--
MOS_MIGRATED_REVID=96158093
|
|
|
|
|
|
|
|
|
| |
This will be used by the persistent JavaBuilder, which improves performance of Java compilation by 4x due to profiting from JVM JIT optimizations and not having to relaunch the JVM for every spawn.
It is completely generic though, so as long as a tool (ProGuard? Dexer? Whatever.) conforms to the Worker process protocol, it can use the new spawn strategy.
--
MOS_MIGRATED_REVID=95527132
|
|
|
|
|
|
|
| |
This is needed so that Bazel can access Android NDK if it's outside of the workspace. The current limitation is that we Bazel can pretend that there is a BUILD file there, but cannot do the same with a CROSSTOOL file. We could fix that limitation, but given that Crosstool is the only conceivable use case, let's fix it by changing the Blaze-Crosstool interface.
--
MOS_MIGRATED_REVID=95517408
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=95285376
|
|
|
|
|
|
|
| |
Too new functionality.
--
MOS_MIGRATED_REVID=95100593
|
|
|
|
|
|
|
|
|
|
|
| |
Packages have the potential to have an exceptional number of associated
targets. When serialized in one message these targets can push the
protocol buffer representation of a Package over the default deserialization
size limit. In this commit we serialize targets separately as a series of
individual messages to avoid this limit.
--
MOS_MIGRATED_REVID=95049743
|
|
|
|
|
|
|
| |
Modify XcodeGen to use that field as workspace root if it is set.
--
MOS_MIGRATED_REVID=94916387
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Generate a srcjar artifact, and use native.java_library to emit the
actual jar file.
Post-review modifications:
- Formatted genproto.bzl
- Use //external:jar instead of relying on PATH
- Make proto library a java_import instead of a filegroup in
test setup.
--
Change-Id: I005f801f09439bbca43e483ad4a47da4588fea94
Reviewed-on: https://bazel-review.googlesource.com/1362
MOS_MIGRATED_REVID=94914935
|