| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
| |
This stops Bazel from passing some of the gcc options to wrapper script.
Options we get rid of:
-c -o -MD -MF -frandom-seed -isystem -iquote -I
--
Change-Id: I416b393c6875a2033d5382a644471c416cd5e8d1
Reviewed-on: https://bazel-review.googlesource.com/#/c/3930
MOS_MIGRATED_REVID=126299789
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126235788
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke builds that use apple_genrule.
*** Original change description ***
Move platform environment from xcrun_action to apple_action.
This change ensures that scripts that don't need to be wrapped with
xcrun_action (like actoolwrapper, ibtoolwrapper, and friends, because
they internally invoke xcrunwrapper) also have the Xcode version and
platform envvars set.
RELNOTES:
--
MOS_MIGRATED_REVID=126205606
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change ensures that scripts that don't need to be wrapped with
xcrun_action (like actoolwrapper, ibtoolwrapper, and friends, because
they internally invoke xcrunwrapper) also have the Xcode version and
platform envvars set.
RELNOTES:
--
MOS_MIGRATED_REVID=126195267
|
|
|
|
|
|
|
|
|
| |
Previously we used labels in each configuration fragment that then got added to every test action. Instead, we now have a filegroup under //tools/test for coverage files that truly need to be on the inputs of every test action and collect language-specific support files in InstrumentedFilesProvider.
This makes configuration creation simpler and makes it possible to turn --crosstool_top into something else other than a filegroup (previously, it was that filegroup that got added to every test action)
--
MOS_MIGRATED_REVID=126170241
|
|
|
|
|
|
|
|
| |
* Passes additional defines and copts specified by objc_ rules to clang from the swift compilation.
* Adds a module cache path flag that equals to the on used by objc_ targets.
--
MOS_MIGRATED_REVID=126099975
|
|
|
|
|
|
|
|
|
| |
merger that is used (legacy or android) is controlled by the manifest_merger attribute on android_binary and the default is controlled by the --android_manifest_merger flag.
RELNOTES: The Android manifest merger is now available as an option for android_binary rules. The merger will honor tools annotations in AndroidManifest.xml and will perform placeholder substitutions using the values specified in android_binary.manifest_values. The merger may be selected by setting the manifest_merger attribute on android_binary.
--
MOS_MIGRATED_REVID=125603954
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125589653
|
|
|
|
|
|
|
| |
Fixes #1403
--
MOS_MIGRATED_REVID=125543227
|
|
|
|
|
|
|
|
|
|
|
| |
manifest merger places the application element as the last child of the manifest element. This is required for Android N.
NEW: fixed index out of range exception
RELNOTES: Merged manifests are guaranteed to have the application element as the last child of the manifest element as required by Android N.
--
MOS_MIGRATED_REVID=125493743
|
|
|
|
|
|
|
| |
--
Change-Id: I9187a50b8070e0615863d1e4f14373c902278489
Reviewed-on: https://bazel-review.googlesource.com/#/c/3851/
MOS_MIGRATED_REVID=125451055
|
|
|
|
|
|
|
|
|
| |
is not picked up when you run the scripts manually using "bash script.sh".
This is also in our shell style guide: "Executables must start with #!/bin/bash and a minimum number of flags. Use set to set shell options so that calling your script as bash <script_name> does not break its functionality."
--
MOS_MIGRATED_REVID=125450962
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-XX:TieredStopAtLevel=1 instead of -client, as the latter is ignored on 64-bit JVMs since at least JDK 6.
The new flags have been shown to cut down CPU time by 50% due to reduced time spent in JIT and improving overall run time for short running actions, some times also cutting them in half.
Here's a benchmark of Bazel building itself, giving a nice 2-4x speedup:
./output/bazel clean && ./output/bazel build //src:bazel
Bazel before this change:
INFO: Elapsed time: 197.783s, Critical Path: 194.10s
INFO: Elapsed time: 198.928s, Critical Path: 195.65s
INFO: Elapsed time: 194.913s, Critical Path: 191.56s
Bazel before this change with --strategy=Javac=worker:
INFO: Elapsed time: 130.436s, Critical Path: 124.27s
INFO: Elapsed time: 116.114s, Critical Path: 112.30s
INFO: Elapsed time: 116.852s, Critical Path: 84.45s
Bazel with this change:
INFO: Elapsed time: 121.625s, Critical Path: 119.08s
INFO: Elapsed time: 119.401s, Critical Path: 115.80s
INFO: Elapsed time: 121.198s, Critical Path: 119.03s
Bazel with this change and --strategy=Javac=worker:
INFO: Elapsed time: 54.456s, Critical Path: 51.28s
INFO: Elapsed time: 53.272s, Critical Path: 51.09s
INFO: Elapsed time: 52.966s, Critical Path: 49.86s
Bazel with this change and --strategy=Javac=worker and stripping -XX:TieredStopAtLevel=1 from JVM flags when using workers:
INFO: Elapsed time: 61.599s, Critical Path: 58.93s
INFO: Elapsed time: 48.695s, Critical Path: 45.02s
INFO: Elapsed time: 46.874s, Critical Path: 43.91s
INFO: Elapsed time: 46.174s, Critical Path: 43.32s
(The latter is a possible optimization for workers and it's also nice to know that the limited tiered compilation does not hurt their performance.)
--
MOS_MIGRATED_REVID=125448089
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a new configuration option that allows disabling the creation of symlink forest for runfiles.
On Windows, symlink forest is disabled by default; only the runfiles manifest is created.
For shell tests, a function 'rlocation' is provided that converts from runfiles location to a real location.
Work towards #1212.
--
MOS_MIGRATED_REVID=125439553
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125429700
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125385321
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke a few projects, including many targets in AGSA: []
*** Original change description ***
Ensure manifest merger places the application element as the last child of the manifest element. This is required for Android N.
RELNOTES: Merged manifests are guaranteed to have the application element as the last child of the manifest element as required by Android N.
--
MOS_MIGRATED_REVID=124960831
|
|
|
|
|
|
|
|
|
| |
the manifest element. This is required for Android N.
RELNOTES: Merged manifests are guaranteed to have the application element as the last child of the manifest element as required by Android N.
--
MOS_MIGRATED_REVID=124954782
|
|
|
|
|
|
|
|
|
|
| |
Without this change, I get the following error:
ERROR: /workspace/WORKSPACE:2:1: new_http_archive rule //external:docker-debian's name field must be a legal workspace name.
I think this naming was made invalid in Bazel 0.1.5
--
MOS_MIGRATED_REVID=124846207
|
|
|
|
|
|
|
| |
tag's name attribute to the Instant Run application class.
--
MOS_MIGRATED_REVID=124606107
|
|
|
|
|
|
|
| |
See https://groups.google.com/d/msgid/bazel-discuss/CAM01fBriKWxwFeb%2B-M80ryJq2Um97N9JZbr5BF7pO-xVa8cL_g%40mail.gmail.com?utm_medium=email&utm_source=footer
--
MOS_MIGRATED_REVID=124543258
|
|
|
|
|
|
|
| |
instead load it from //external.
--
MOS_MIGRATED_REVID=124480945
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Docker 1.10 updated the format of images moving layers to just being
tarballs referenced by a configuration file. A new manifest.json file
aggregates images and handles parent and tagging references. Layers and
images are now identified by their sha256 hash. An image configuration
file must reference all layers that belong to it by this identifier,
including all layers in any parent images.
Image configuration is generated the same way but now allows multiple
layer sha256 hashes to be provided. The base image configuration is read
to find config defaults and the layer identifiers that need to be
present.
Image creation now requires the layer identifier and file and can accept
multiple layers. A manifest with a single entry is created that points
at the image configuration, its layers and tags. If a base image is
provided its layers are added to the begining of the layer section and a
parent reference to the base image is added. Multiple tags can be
provided which are applied when the image is loaded.
The joining of partial images now consists of merging their contents
minus the manifest which is concatentated together.
These changes have been made in a backwards compatible way so versions
of docker below 1.10 will still work as before.
Fixes #1113
--
Change-Id: I0075decc48d8846ad16431948192db196ad702ee
Reviewed-on: https://bazel-review.googlesource.com/3730
MOS_MIGRATED_REVID=124339578
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Cannot be built with currently released Bazel.
*** Original change description ***
Remove redirect chasing from AndroidConfiguration.Loader.
With aliases, it's not necessary anymore.
--
MOS_MIGRATED_REVID=124123904
|
|
|
|
|
|
|
| |
for the C++ toolchain.
--
MOS_MIGRATED_REVID=124111346
|
|
|
|
|
|
|
| |
* This eliminates the need to put "dummy.swift" into objc_binary targets that depend on swift_library.
--
MOS_MIGRATED_REVID=124015750
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=123971774
|
|
|
|
|
|
|
|
|
|
|
| |
The Docker USER parameter[1] specifies the system user that the contained
process will run under, amoungst other things. The |docker_build| function
already has an argument for this, but it was previously ignored.
[1] https://docs.docker.com/engine/reference/builder/#user
--
MOS_MIGRATED_REVID=123782558
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=123663717
|
|
|
|
|
|
|
| |
Fixes #1316.
--
MOS_MIGRATED_REVID=123655074
|
|
|
|
|
|
|
| |
Fixes the android part of #1316.
--
MOS_MIGRATED_REVID=123644129
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This might causes problem in a future remote execution services but
in that kind of service it would make more sense to not use the
auto-configured C++ toolchain.
Tested with bazel test //tools/cpp/test:*
Fixes #1204.
--
MOS_MIGRATED_REVID=123643630
|
|
|
|
|
|
|
|
| |
* Modules are now named after its full target path by default.
* module_name attribute can be used to override this logic.
--
MOS_MIGRATED_REVID=123422704
|
|
|
|
|
|
|
|
|
|
| |
* Adds a way to read FRAMEWORK_ keys from ObjcProvider and provide outputs as -F args to the compiler
* Adds a sample dynamic framework for testing
RELNOTES: swift_library is now able to import framework rules such as objc_framework.
--
MOS_MIGRATED_REVID=123337139
|
|
|
|
|
|
|
|
|
| |
* General cleanup of the rule code.
* Adds a way to use modulemaps to import Objective-C code.
* Adds a way to pass framework flags to the compiler and adds the developer frameworks dir from Xcode as one.
--
MOS_MIGRATED_REVID=123217120
|
|
|
|
|
|
|
| |
dependencies through the ObjcProtoAspect, compiling and linking the generated protos at the final linking target. This is only enabled for objc_proto_libraries using the portable_proto_filters attribute, and guarded with the "--experimental_auto_top_level_union_objc_protos" flag. This prevents duplicate symbol errors as the generated sources are only linked once.
--
MOS_MIGRATED_REVID=123144532
|
|
|
|
|
|
|
| |
around apple's buggy libtool tool
--
MOS_MIGRATED_REVID=123024674
|
|
|
|
|
|
|
|
|
| |
Removes an old code path that is not relevant anymore.
RELNOTES:
--
MOS_MIGRATED_REVID=122534499
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, _short_path_dirname would take a short path like "libfoo.jar",
rfind would return -1, sp[:-1] would return "libfoo.ja", and then
_dest_path would strip that prefix off of "libfoo.jar", leaving just "r".
Also added some unit tests for these functions.
Fixes #1253.
--
MOS_MIGRATED_REVID=122527723
|
|
|
|
|
|
|
| |
Fixes #1269
--
MOS_MIGRATED_REVID=122502116
|
|
|
|
|
|
|
|
|
| |
* Switches the rule to output to genfiles/, this makes C-headers it produces importable by depending targets.
RELNOTES: swift_library now generates an Objective-C header for its @objc interfaces.
--
MOS_MIGRATED_REVID=122448949
|
|
|
|
|
|
|
|
|
| |
It is now consistent with CPU.java
Fixes #1251.
--
MOS_MIGRATED_REVID=122036487
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=121953905
|
|
|
|
|
|
|
| |
--
Change-Id: If41817e3889f118a849a29cfb03ac0f7e07d5557
Reviewed-on: https://bazel-review.googlesource.com/#/c/3582
MOS_MIGRATED_REVID=121924420
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
only if in homebrew
This will fix the sandboxing issues for rules_rust and rules_go while still allowing to build inside homebrew.
Should unblock #1238
Fixes bazelbuild/rules_go#20.
Fixes bazelbuild/rules_rust#4.
Tested under homebrew + classic tests.
--
MOS_MIGRATED_REVID=121834186
|
|
|
|
|
|
|
|
| |
Those rules were moved to, respectively, https://github.com/bazelbuild/rules_rust,
https://github.com/bazelbuild/rules_jsonnet, https://github.com/bazelbuild/rules_scala, and https://github.com/bazelbuild/rules_closure.
--
MOS_MIGRATED_REVID=121834063
|
|
|
|
|
|
|
| |
gRPC is only used for intra-machine communications, for which not using crypto is perfectly fine.
--
MOS_MIGRATED_REVID=121825070
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
local instance of bazel.io site.
* Add a new genrule rule that runs the new jekyll-tree.sh to do the following:
* Combine the generated docs for the Build Encyclopedia and Skylark Library
with the static site docs
* Combine the README.md files for the Docker and Packaging rules with the
Jekyll tree
* Process the generated docs, replaces instances of "blaze" with "bazel",
etc.
* Add scripts/serve-docs.sh script that can be used to bring up a local
instance of the bazel.io website.
As of this patch, it is possible to construct the full Bazel.io site tree from
the master branch.
--
MOS_MIGRATED_REVID=121813688
|
|
|
|
|
|
|
|
|
| |
android_sdk_repository so that preview sdks can be correctly handled. For example, the name in the build-tools directory might be "24.0.0-preview", but its version is actually "24 rc3" from build-tools/24.0.0-preview/source.properties.
Fixes https://github.com/bazelbuild/bazel/issues/1240
--
MOS_MIGRATED_REVID=121719519
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll-forward with fix:
- Previous test did let the all_files group with the wrapper script, and it got removed when creating the actual change. Added it back
Tested with `./compile.sh determinism`
*** Original change description ***
Automated [] rollback of commit 87a58589d6770a6e9a0f998274bfe69f1feb6014.
*** Reason for rollback ***
The sandbox fix did not fix. More work is needed.
Fixes #1239
*** Original change description ***
Automated [] rollback of commit b4549fe8dfb29f87fd37b38bf21a5b4bef818b12.
*** Reason for rollback ***
Rollforward with fixes:
- Quote single-quote in the environment exports
- Exclude the following environment variables: _ and dotted names
- Add the wrapper to the dependency of the crosstool chain so it gets shipped to the sandbox.
Hopefu...
--
MOS_MIGRATED_REVID=121667505
|