| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now Bazel can detect MSVC from Visual Studio 2017 or Visual C++ build
tools 2017.
Also modified build_windows_jni.sh to make it work with VS 2017.
Fixed: https://github.com/bazelbuild/bazel/issues/2440
--
Change-Id: I4afbce809ff74634f32fab87efe5e7f0b3f60c95
Reviewed-on: https://cr.bazel.build/8890
PiperOrigin-RevId: 147467993
MOS_MIGRATED_REVID=147467993
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 147449557
MOS_MIGRATED_REVID=147449557
|
|
|
|
|
|
|
|
| |
Creates filegroup containing sdk path in Bazel embedded Android SDK repository.
--
PiperOrigin-RevId: 147426838
MOS_MIGRATED_REVID=147426838
|
|
|
|
|
|
|
|
|
|
| |
This caused a failure in http://ci.bazel.io/job/Gerrit-bazel-tests/368/BAZEL_VERSION=latest,PLATFORM_NAME=ubuntu_15.10-x86_64/console
where the genrule used java from a jdk7 instead of a jdk8.
--
PiperOrigin-RevId: 147198518
MOS_MIGRATED_REVID=147198518
|
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/2222.
RELNOTES: Support for Java 8 lambdas, method references, type annotations and repeated annotations in Android builds with --experimental_desugar_for_android.
--
PiperOrigin-RevId: 147109786
MOS_MIGRATED_REVID=147109786
|
|
|
|
|
|
|
|
|
|
|
|
| |
//third_party/protobuf:protobuf to refer to the Java proto runtime.
(second attempt)
This is the name in the upstream protobuf repo.
--
PiperOrigin-RevId: 147057949
MOS_MIGRATED_REVID=147057949
|
|
|
|
|
|
|
|
| |
list / always a scalar.
--
PiperOrigin-RevId: 147051864
MOS_MIGRATED_REVID=147051864
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 147039153
MOS_MIGRATED_REVID=147039153
|
|
|
|
|
|
|
|
| |
Then use it in the blaze plugin's main class run configuration producer.
--
PiperOrigin-RevId: 146980092
MOS_MIGRATED_REVID=146980092
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolling forward with fixes for the incremental tool.
*** Original change description ***
Automated [] rollback of commit d11d510c571b10787856395709f9ad945ca70bb2.
*** Reason for rollback ***
--
PiperOrigin-RevId: 146940409
MOS_MIGRATED_REVID=146940409
|
|
|
|
|
|
|
|
|
|
|
| |
See: https://github.com/bazelbuild/bazel/issues/2434
Fixed https://github.com/bazelbuild/bazel/issues/2448
--
Change-Id: I12b109af81e0eb8948fd1d7a7d2bbfcf6baa7ca4
Reviewed-on: https://cr.bazel.build/8693
PiperOrigin-RevId: 146886981
MOS_MIGRATED_REVID=146886981
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
--
PiperOrigin-RevId: 146820790
MOS_MIGRATED_REVID=146820790
|
|
|
|
|
|
|
|
|
| |
This makes the code simpler as well as reducing the number of targets to build.
It also makes testing and profiling different action strategies vastly easier.
--
PiperOrigin-RevId: 146812659
MOS_MIGRATED_REVID=146812659
|
|
|
|
|
|
|
|
|
|
|
| |
These changes addresses issues where Windows users have a space in their username. Allows the default output_base path to be used.
Closes #2491.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2491
PiperOrigin-RevId: 146773331
MOS_MIGRATED_REVID=146773331
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In almost every place we compared paths against
MAX_PATH, we had it wrong. MAX_PATH is the
null-terminated maximum length, so paths exactly
MAX_PATH long (not counting the null-terminator)
were incorrectly considered short.
Also fix the error message in the MSVC python
wrapper, because it reported an incorrect path
length limit in the warning message.
See https://github.com/bazelbuild/bazel/issues/2107
--
PiperOrigin-RevId: 146762382
MOS_MIGRATED_REVID=146762382
|
|
|
|
|
|
|
|
| |
added by default as -framework arguments when linking. This enables test bundles on not having to relink static frameworks that were also linked in to the test host app.
--
PiperOrigin-RevId: 146713403
MOS_MIGRATED_REVID=146713403
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Header compilation is now explicitly disabled for JDK 7 Bazel using java_toolchain.forcibly_disable_header_compilation
*** Original change description ***
Automated [] rollback of commit 156adeec613ab140a91d73e1147bc688689bcfb7.
*** Reason for rollback ***
Breaks Bazel on JDK 7: http://ci.bazel.io/view/Dashboard/job/bazel-tests/BAZEL_VERSION=HEAD-jdk7,PLATFORM_NAME=linux-x86_64/475/console
*** Original change description ***
Automated [] rollback of commit 5163ec2c0db8fbdc7f367bb4aca5b6d7ae6d80b0.
*** Reason for rollback ***
See unknown commit
*** Original change description ***
Automated [] rollback of commit c9dbd4c1a4a4b4345c0b3924f86e01612ae12807.
*** Reason for rollback ***
Breaks bazel-docker-tests
http://ci.baz...
***
--
PiperOrigin-RevId: 146685610
MOS_MIGRATED_REVID=146685610
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146508452
MOS_MIGRATED_REVID=146508452
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES: Adds pkg_rpm rule for generating RPM packages.
--
Change-Id: I2e83161e29218700bbe7e62186b0b1667e555a7c
Reviewed-on: https://cr.bazel.build/8590
PiperOrigin-RevId: 146477490
MOS_MIGRATED_REVID=146477490
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146385106
MOS_MIGRATED_REVID=146385106
|
|
|
|
|
|
|
|
|
| |
These were getting annoying as they trigger when
you edit code near the offending lines.
--
PiperOrigin-RevId: 146381829
MOS_MIGRATED_REVID=146381829
|
|
|
|
|
|
|
|
| |
These are not used anymore.
--
PiperOrigin-RevId: 146381129
MOS_MIGRATED_REVID=146381129
|
|
|
|
|
|
|
|
| |
Identified in https://github.com/bazelbuild/bazel/issues/1408.
--
PiperOrigin-RevId: 146308540
MOS_MIGRATED_REVID=146308540
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146300001
MOS_MIGRATED_REVID=146300001
|
|
|
|
|
|
|
|
| |
No need to confusingly separate out providers and pollute the namespace -- instead collect everything under the "intellij_info" provider.
--
PiperOrigin-RevId: 146279148
MOS_MIGRATED_REVID=146279148
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollforward with fixes and a test. Previously AndroidSdkRepository required that system-images/ directory exist in the Android SDK. However, it does not exist until you download the first system image.
*** Original change description ***
Automated [] rollback of commit 06072c557290b97cb2d2e4fd255b647a9208cb5c.
*** Reason for rollback ***
Broke andriod_sdk_repository on ci.bazel.io
See https://github.com/bazelbuild/bazel/issues/2465
*** Original change description ***
Make android_sdk_repository discover all system-images directories in the sdk.
This will be used by the upcoming android_device rule that launches emulators.
--
PiperOrigin-RevId: 146258003
MOS_MIGRATED_REVID=146258003
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke andriod_sdk_repository on ci.bazel.io
See https://github.com/bazelbuild/bazel/issues/2465
*** Original change description ***
Make android_sdk_repository discover all system-images directories in the sdk.
This will be used by the upcoming android_device rule that launches emulators.
--
PiperOrigin-RevId: 146235800
MOS_MIGRATED_REVID=146235800
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the BAZEL_SH envvar while creating the Windows
CROSSTOOL file, instead of calling "cygpath -m /".
The latter is based on the assumption that we are
running under MSYS.
Fixes https://github.com/bazelbuild/bazel/issues/2463
See https://github.com/bazelbuild/bazel/issues/2107
--
PiperOrigin-RevId: 146227581
MOS_MIGRATED_REVID=146227581
|
|
|
|
|
|
|
|
| |
This will be used by the upcoming android_device rule that launches emulators.
--
PiperOrigin-RevId: 146183077
MOS_MIGRATED_REVID=146183077
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146142811
MOS_MIGRATED_REVID=146142811
|
|
|
|
|
|
|
|
| |
Note that these aliases are intentionally not yet functional. Nothing should be trying to build them.
--
PiperOrigin-RevId: 145746166
MOS_MIGRATED_REVID=145746166
|
|
|
|
|
|
|
|
| |
attributes if they aren't present in the original manifest. Before, it would make them None, and aapt would fail.
--
PiperOrigin-RevId: 145726642
MOS_MIGRATED_REVID=145726642
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed #2433
Working towards #1897
--
Change-Id: I62ed4eabac5c788f90b10e9dfe4c9ffee6883097
Reviewed-on: https://cr.bazel.build/8492
PiperOrigin-RevId: 145675987
MOS_MIGRATED_REVID=145675987
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The effect of this change on Bazel is that we now set the entire list of
env variables needed for the various protocols: sharding protocol, undeclared
outputs protocol, test warnings, unused runfiles, premature exit signalling,
and coverage. We also now set TEST_SIZE, TEST_TIMEOUT, and TEST_RANDOM_SEED.
I'm not sure if all of the Bazel-side infrastructure for those protocols is
ready yet. With further progress on code sharing, they should fall into place
soon, though.
Also set GUNIT_OUTPUT for now. Ideally, we'd change upstream to accept our
more generic names, but this should do for now.
--
PiperOrigin-RevId: 145660945
MOS_MIGRATED_REVID=145660945
|
|
|
|
|
|
|
|
| |
Fixed https://github.com/bazelbuild/bazel/issues/2415
--
PiperOrigin-RevId: 145530562
MOS_MIGRATED_REVID=145530562
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I have tested on NVIDA Jetson TK1 and bazel was able to compile.
I believe with this quick fix would make bazel installation on Linux ARM devices easier. I have been spending 5 hours to figure out a correct way to install bazel.
Closes #2389.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2389
PiperOrigin-RevId: 145401787
MOS_MIGRATED_REVID=145401787
|
|
|
|
|
|
|
|
| |
Fixes #2405
--
PiperOrigin-RevId: 145394624
MOS_MIGRATED_REVID=145394624
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Strip quotes from arg0 in call_python.bat .
This bug was has been there longer, but never got
triggered, because we only quoted arg0 if it
contained spaces, which it most likely never
actually did, or not in this particular case.
After submitting e68c6b5 and 9e8bc63 which fixed
the compilation errors in the former, we started
always quoting argv0 in subprocesses, which
exposed this bug, leading to a corrupt DRIVER_DIR
value in call_python.bat.
Fixes https://github.com/bazelbuild/bazel/issues/2402
--
Change-Id: Iab5c00001fc4307f2e23c46c8187f5ef15d83d41
Reviewed-on: https://cr.bazel.build/8436
PiperOrigin-RevId: 145310121
MOS_MIGRATED_REVID=145310121
|
|
|
|
|
|
|
|
| |
to behind the terminal when using blaze run ios_app_target.
--
PiperOrigin-RevId: 145279294
MOS_MIGRATED_REVID=145279294
|
|
|
|
|
|
|
|
|
|
| |
This cl relieves us from hard-coding -l and -l: flags in Bazel. To be able to
express the behavior in CROSSTOOL, we need to know what type of library are we
dealing with.
--
PiperOrigin-RevId: 145271426
MOS_MIGRATED_REVID=145271426
|
|
|
|
|
|
|
|
| |
Saves 12kB! :)
--
PiperOrigin-RevId: 144997917
MOS_MIGRATED_REVID=144997917
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Classifier should be provided in the form:
"groupId:artifactId:version[:packaging][:classifier]"
because that's what maven-dependency-plugin expects and not in the form:
"groupId:artifactId[:packaging][:classifier]:version"
as documented here: [1]. Also it was missed to reflect the classifier in
the output artifact name.
TEST PLAN:
WORKSPACE:
load("//tools:maven_rules.bzl", "maven_jar",
"maven_dependency_plugin")
maven_dependency_plugin()
maven_jar(
name = "jetty_server_sources",
artifact = "org.eclipse.jetty:jetty-server:9.3.11.v20160721:jar:sources",
sha1 = "b23cac190808baed928260b2c9beca3b1ed232b4",
)
BUILD:
java_library(
name = "jetty-server-sources",
exports = ["@jetty_server_sources//jar"],
)
$ bazel build :jetty-server-sources
[...]
Target //:jetty-server-sources up-to-date:
bazel-bin/libjetty-server-sources.jar
[1] https://maven.apache.org/pom.html#Maven_Coordinates
Fixes #2049.
--
Change-Id: I3297fb3676324cc6b4bb6ff6b2b6e18ce33f633c
Reviewed-on: https://cr.bazel.build/7213
PiperOrigin-RevId: 144972944
MOS_MIGRATED_REVID=144972944
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144965639
MOS_MIGRATED_REVID=144965639
|
|
|
|
|
|
|
|
|
|
| |
Fixes #2360.
--
Change-Id: I33dcfa1128b74f20dde14c5b5e095790a8961bd5
Reviewed-on: https://cr.bazel.build/8219
PiperOrigin-RevId: 144685099
MOS_MIGRATED_REVID=144685099
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Bazel on JDK 7: http://ci.bazel.io/view/Dashboard/job/bazel-tests/BAZEL_VERSION=HEAD-jdk7,PLATFORM_NAME=linux-x86_64/475/console
*** Original change description ***
Automated [] rollback of commit 5163ec2c0db8fbdc7f367bb4aca5b6d7ae6d80b0.
*** Reason for rollback ***
See unknown commit
*** Original change description ***
Automated [] rollback of commit c9dbd4c1a4a4b4345c0b3924f86e01612ae12807.
*** Reason for rollback ***
Breaks bazel-docker-tests
http://ci.bazel.io/view/Dashboard/job/bazel-docker-tests/lastCompletedBuild/BAZEL_VERSION=HEAD,PLATFORM_NAME=docker/console
*** Original change description ***
Enable header compilation by default
--
PiperOrigin-RevId: 144443446
MOS_MIGRATED_REVID=144443446
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
See unknown commit
*** Original change description ***
Automated [] rollback of commit c9dbd4c1a4a4b4345c0b3924f86e01612ae12807.
*** Reason for rollback ***
Breaks bazel-docker-tests
http://ci.bazel.io/view/Dashboard/job/bazel-docker-tests/lastCompletedBuild/BAZEL_VERSION=HEAD,PLATFORM_NAME=docker/console
*** Original change description ***
Enable header compilation by default
--
PiperOrigin-RevId: 144344329
MOS_MIGRATED_REVID=144344329
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
api_level is no longer required. It now sets the default android_sdk that is used if the --android_sdk flag is not passed. If it is not set, the highest api_level will be used as the default.
The new behavior is demonstrated by the following example:
$ ls $ANDROID_HOME/platforms
android-21 android-22 android-23
$ cat WORKSPACE
android_sdk_repository(
name = "foo",
)
$ bazel build //java/my/app # uses api level 23
$ bazel build --android_sdk=@foo//:sdk-22 //java/my/app # uses api level 22
$ cat > WORKSPACE <<EOF
android_sdk_repository(
name = "foo",
api_level = 21,
)
EOF
$ bazel build //java/my/app # uses api level 21
$ bazel build --android_sdk=@foo//:sdk-23 //java/my/app # uses api level 23
See https://github.com/bazelbuild/bazel/issues/2284 for the master plan for android_sdk_repository.
RELNOTES: android_sdk_repository no longer requires api_level. If one is not specified, the highest android platform installed will be used. Furthermore, android_sdk's are created for all android platforms installed and can be specified with the --android_sdk flag.
--
PiperOrigin-RevId: 144258881
MOS_MIGRATED_REVID=144258881
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144231300
MOS_MIGRATED_REVID=144231300
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks bazel-docker-tests
http://ci.bazel.io/view/Dashboard/job/bazel-docker-tests/lastCompletedBuild/BAZEL_VERSION=HEAD,PLATFORM_NAME=docker/console
*** Original change description ***
Enable header compilation by default
--
PiperOrigin-RevId: 144176396
MOS_MIGRATED_REVID=144176396
|
|
|
|
|
|
|
|
|
|
| |
source jars.
In the j2objc dead code removal script, quote the object file names when invoking ar. They may contain special shell characeters.
--
PiperOrigin-RevId: 143993977
MOS_MIGRATED_REVID=143993977
|