| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix https://github.com/bazelbuild/bazel/issues/2075
The logic for constructing nvcc options is from:
third_party/gpus/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc.tpl
in TensorFlow repo.
To make things configurable, this change makes cc_configure.bzl depend on more
environment variables:
CUDA_PATH: This variable points to Cuda installation directory
CUDA_COMPUTE_CAPABILITIES: Specifiy cuda compute capabilities
NO_WHOLE_ARCHIVE_OPTION: if set to 1, /WHOLEARCHIVE option won't be used.
--
Change-Id: Ib1610a6d3423ca55a27c7a0f438703c05630a85c
Reviewed-on: https://cr.bazel.build/7351
MOS_MIGRATED_REVID=139903436
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks bazel: http://ci.bazel.build/job/bazel-tests/329/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/console
*** Original change description ***
Support gold linker
--
MOS_MIGRATED_REVID=139810019
|
|
|
|
|
|
|
|
| |
This will allow use of the Skylark IDE aspect in bazel,
unblocking the migration away from the native aspect.
--
MOS_MIGRATED_REVID=139796095
|
|
|
|
|
|
|
| |
RELNOTES: Skylark implementations of http_archive, new_http_archive, and http_file.
--
MOS_MIGRATED_REVID=139633771
|
|
|
|
|
|
|
| |
This should allow to use pkg_tar from project that use python 3 (e.g. TensorFlow).
--
MOS_MIGRATED_REVID=139561406
|
|
|
|
|
|
| |
--
Reviewed-on: https://bazel-review.googlesource.com/c/7372/
MOS_MIGRATED_REVID=139432850
|
|
|
|
|
|
|
| |
RELNOTES:
--
MOS_MIGRATED_REVID=139370787
|
|
|
|
|
|
|
| |
Now, apks can be built faster in Bazel using the --use_singlejar_apkbuilder flag.
--
MOS_MIGRATED_REVID=139285943
|
|
|
|
|
|
|
| |
Also stop silently creating empty archives if the output archives do not exist (!).
--
MOS_MIGRATED_REVID=138778978
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/561.
To use this rule, you will need to include the following line in your WORKSPACE file:
load("@bazel_tools//tools/build_defs/repo:maven_rules.bzl", "maven_aar")
After that, you can use the maven_aar repository rule in your WORKSPACE file as such:
maven_aar(
name = "facebook_android_sdk",
artifact = "com.facebook.android:facebook-android-sdk:3.19.0",
)
Then in your BUILD files, your android_library and android_binary targets can depend on the AAR with the following syntax:
android_binary(
name = "my_app",
...
deps = [
"@facebook_android_sdk//aar",
...
],
)
The resources, classes and native libs from the AAR will be provided. Note however that some features of AAR files are not yet supported, including assets, Proguard maps and lint jars.
--
MOS_MIGRATED_REVID=138575421
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138516288
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Use proto_lang_toolchain() in java_proto_library, after fixing breakage.
Verified on Jenkins, http://ci.bazel.io/job/Gerrit-bazel-tests/169/
*** Original change description ***
Automated [] rollback of commit a396b070ae36032a973672e11145533621c39edc.
*** Reason for rollback ***
Breaks tests on latest, as proto_lang_toolchain didn't make it into the 0.4.0 release
see http://ci.bazel.io/job/bazel-tests/306/BAZEL_VERSION=latest,PLATFORM_NAME=linux-x86_64/console
*** Original change description ***
Use proto_lang_toolchain() in java_proto_library.
--
MOS_MIGRATED_REVID=138432193
|
|
|
|
|
|
|
|
|
|
|
|
| |
No need to use double back slash.
This could help ease the Windows long path issue.
Please see https://github.com/tensorflow/tensorflow/pull/5385
--
Change-Id: Iecca529209499062bfc1351e3a2b46dc51e0be09
Reviewed-on: https://bazel-review.googlesource.com/#/c/7210
MOS_MIGRATED_REVID=138397390
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks tests on latest, as proto_lang_toolchain didn't make it into the 0.4.0 release
see http://ci.bazel.io/job/bazel-tests/306/BAZEL_VERSION=latest,PLATFORM_NAME=linux-x86_64/console
*** Original change description ***
Use proto_lang_toolchain() in java_proto_library.
--
MOS_MIGRATED_REVID=138372522
|
|
|
|
|
|
|
| |
* This change removes forced -parse-as-library mode in favor of the driver figuring out how to parse each source. This means that main.swift will be parsed as a script and can contain top-level expressions.
--
MOS_MIGRATED_REVID=138285669
|
|
|
|
|
|
|
| |
Clear certain environment variables on xcrun invocation to generate xcode-locator-bin, and provide additional error output if the invocation should fail.
--
MOS_MIGRATED_REVID=138221908
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138161512
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138104480
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138005602
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137500893
|
|
|
|
|
|
|
|
| |
Prior to this change, the android SDK for the integration tests was empty so
they were not run.
--
MOS_MIGRATED_REVID=137307968
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137291831
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137209855
|
|
|
|
|
|
|
|
|
|
|
| |
In commit 78c19807d2cbb308b830022dcdcc8b03f19f90a9 I accidentally broke aar_import when I moved
zip_manifest_creator from tools/android to tools/zip because tools/android does
not have separate BUILD and BUILD.tools files. The test did not catch this,
because the dependency in tools/android/BUILD is correct in the context of the
bazel tree but not in the context of the bazel_tools embedded workspace.
--
MOS_MIGRATED_REVID=137209500
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/1935
--
MOS_MIGRATED_REVID=137202533
|
|
|
|
|
|
|
| |
The libs that are extracted are dependent on the CPU from the Android split transition. This is set either from --fat_apk_cpu or --android_cpu if fat_apk_cpu is empty.
--
MOS_MIGRATED_REVID=137188695
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use wrapper script to get object files if /WHOLEARCHIVE is not supported.
fix https://github.com/bazelbuild/bazel/issues/1978
work towards https://github.com/bazelbuild/bazel/issues/1918
--
Change-Id: I675311478e65a1e1f3fa963187a5a8da531150d3
Reviewed-on: https://bazel-review.googlesource.com/#/c/6833
MOS_MIGRATED_REVID=137151817
|
|
|
|
|
|
|
| |
Default architectures expanded to cover all the architectures that we build.
--
MOS_MIGRATED_REVID=136856770
|
|
|
|
|
|
|
| |
* Remove obsolete code paths and format the file to keep 2 lines between top-level methods.
--
MOS_MIGRATED_REVID=136842040
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=136837274
|
|
|
|
|
|
|
|
| |
* This change enables most of LLDB functionality on binaries built by swift_library.
It makes the linker record references to the .swiftmodule outputs, which then can be read by LLDB to deserialize Swift modules and provide debug info.
--
MOS_MIGRATED_REVID=136620475
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Causes huge memory blow-up after the analysis phase in CppLinkAction (LinkCommandLine).
--
MOS_MIGRATED_REVID=136467836
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=136416405
|
|
|
|
|
|
|
| |
--
Change-Id: I46e434e9add5647bd29945ba2f80a399999a4b17
Reviewed-on: https://bazel-review.googlesource.com/#/c/6692
MOS_MIGRATED_REVID=136325160
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=136161771
|
|
|
|
|
|
|
| |
Also moves AAR-specific tools from tools/zip into tools/android and renames embedded_jar_extractor to aar_embedded_jars_extractor because in a future change it will extract classes.jar and libs/*.jar.
--
MOS_MIGRATED_REVID=136099324
|
|
|
|
|
|
|
| |
annotation processing support.
--
MOS_MIGRATED_REVID=136084697
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This feature is needed when linking the _pywrap_tensorflow.dll on Windows.
Which will force link all the libraries in deps.
I used /WHOLEARCHVIE to implement this, so it only works with Visual Stduio
2015 update 2 or later.
--
Change-Id: I0b018d3f4f482e56d1ebf78faa08fa46e1d60bbf
Reviewed-on: https://bazel-review.googlesource.com/#/c/6612
MOS_MIGRATED_REVID=135923622
|
|
|
|
|
|
|
| |
* This produces more human-readable error messages in cases where sources are omitted (e.g. if a glob matches nothing).
--
MOS_MIGRATED_REVID=135920885
|
|
|
|
|
|
|
|
|
| |
Currently, TensorFlow only supports python3.5 on Windows.
--
Change-Id: Ia3e805a7fdca06b79d9c00b0a2e83b9dd41e5f78
Reviewed-on: https://bazel-review.googlesource.com/#/c/6611
MOS_MIGRATED_REVID=135919759
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/bazel/test-setup.sh uses this filegroup to symlink the contents
of the Android SDK into the workspace for the test. However, since we add BUILD
files into the Android SDK, we don't want to copy those into the workspace
because they will be regenerated by the integration test.
Fixes https://github.com/bazelbuild/bazel/issues/1927.
--
MOS_MIGRATED_REVID=135858750
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135805730
|
|
|
|
|
|
|
|
|
| |
This cl moves the conditional building of interface libraries from LinkCommandLine to action configs and features. It provides link_dynamic_library.sh to keep blaze backwards compatible. The script and related code can be deleted once all crosstools are updated.
RELNOTES: No.
--
MOS_MIGRATED_REVID=135799041
|
|
|
|
|
|
|
| |
The previous solution added too many unneeded runfiles, which caused problems with our workers.
--
MOS_MIGRATED_REVID=135782773
|
|
|
|
|
|
|
|
|
|
|
| |
We have added support for Linux s390x platform in Bazel.
Closes #1891.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1891
MOS_MIGRATED_REVID=135777047
|
|
|
|
|
|
|
| |
* This mimics the behavior of cc_ and objc_ library rules.
--
MOS_MIGRATED_REVID=135710506
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135689610
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135686367
|
|
|
|
|
|
|
| |
jar file instead of crashing Bazel.
--
MOS_MIGRATED_REVID=135405636
|
|
|
|
|
|
|
|
|
|
|
| |
I'm not sure how this got all crazy the last time I touched this file!
This restores the earlier sane line wrapping. Changes are purely
whitespace.
--
Change-Id: I6bc743de132be74b1be64c45fceba73315d06e72
Reviewed-on: https://bazel-review.googlesource.com/c/5750/
MOS_MIGRATED_REVID=135365348
|