| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Fixes #1122.
--
MOS_MIGRATED_REVID=120223970
|
|
|
|
|
|
|
| |
Fixes #760.
--
MOS_MIGRATED_REVID=120217217
|
|
|
|
|
|
|
|
|
|
|
|
| |
cc_configure assumed the paths returned by $(CC) -E -xc++ -v
where not containing any extra information but clang on OS X
adds " (framework directory)" for path from Frameworks. This
change strip this out.
--
Change-Id: I90617e825100f86a1f0991e128755802da2c7afd
Reviewed-on: https://bazel-review.googlesource.com/3389
MOS_MIGRATED_REVID=120210800
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change disables --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top, and finishes replacing them with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}.
RELNOTES: Replace --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}
--
MOS_MIGRATED_REVID=120154954
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119986133
|
|
|
|
|
|
|
| |
It appears as though the --objc_generate_debug_symbols flag generates a viable dSYM bundle before the build is failed by this stub script. This change makes the stub a warning instead of an error so that users can utilize the generated dSYM to do debugging.
--
MOS_MIGRATED_REVID=119958618
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks ci.bazel.io
While the basics for fixing the build is easy (just a few typos in packages building), fixing the test is a bit more tricky. I see only one solution for fixing the test: use a select statement that would select the good bazel version but that would always pull JavaBuilder as an external dependency when we do test.
Better roll this back then check the JavaBuilder 0.1.0 as a binary in third_party before rolling forward (a similar change is still needed to decouple running the test and building the binary for JDK 7)
*** Original change description ***
Refactor build for JDK 7
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
MOS_MIGRATED_REVID=119773123
|
|
|
|
|
|
|
|
|
|
|
| |
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
Change-Id: Iff590c6642ca5b2343aa15096f8fd837d1c80787
Reviewed-on: https://bazel-review.googlesource.com/#/c/3327
MOS_MIGRATED_REVID=119634530
|
|
|
|
|
|
|
|
|
| |
This is mainly so that Dash can be fixed. It's not the optimal solution because then Dash will pull in the whole Bazel repository for a tiny little part of it, though. The optimal solution would be to make Bazel use WORKSPACE dependencies and then factor it out to a separate repository, but this will be good enough to unbreak Dash for the time being.
Progress toward fixing https://github.com/bazelbuild/dash/issues/12 .
--
MOS_MIGRATED_REVID=119633183
|
|
|
|
|
|
|
|
|
| |
Also fixed a small bug.
--
Change-Id: I05dab2f4a5d6216f2972b0cd2cb62506f5b1cb06
Reviewed-on: https://bazel-review.googlesource.com/#/c/3326/
MOS_MIGRATED_REVID=119529809
|
|
|
|
|
|
|
| |
I carefully kept the test_rules.bzl file but managed to omit the corresponding BUILD file from the embedded tools zip.
--
MOS_MIGRATED_REVID=119523076
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119518388
|
|
|
|
|
|
|
|
|
|
|
|
| |
The immmediate reason for this change is that we also need to add gRPC support to the proto rules, and we don't want to also support gRPC in a half-baked way.
This makes the Bazel binary much smaller and avoid giving false signals that we (for now) support protobuf compilation. The protobuf rules are only for compiling Bazel itself.
RELNOTES[INC]: Bazel does not embed protocol buffer-related rules anymore.
--
MOS_MIGRATED_REVID=119516246
|
|
|
|
|
|
|
| |
Windows currently means msys2, and the tools there do support params files, and BoringSSL cannot be compiled without them because command lines are too long.
--
MOS_MIGRATED_REVID=119360154
|
|
|
|
|
|
|
| |
in Android SDK build tools version 24.0.0.
--
MOS_MIGRATED_REVID=119305998
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch add the msvc crosstool definiton to CROSSTOOL file and BUILD file.
Two paths are expected to exist:
for msvc: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/
for windows sdk: C:/Program Files (x86)/Windows Kits/10/
--
Change-Id: I2b21e566a588459f9fef767c5dc9dab1565d1ae8
Reviewed-on: https://bazel-review.googlesource.com/#/c/3266
MOS_MIGRATED_REVID=119276027
|
|
|
|
|
|
|
|
|
|
| |
Using batch script to invoke real wrapper script written in python
The default python path is expected to be C:/python_27_amd64/files/python.exe
--
Change-Id: If47bf668ce4af2b6d28a1852189c061480816833
Reviewed-on: https://bazel-review.googlesource.com/#/c/3265
MOS_MIGRATED_REVID=119275909
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks //src/test/shell/bazel:bazel_example_test because that relies on the protobuf rules depending on @bazel_tools . The correct solution is probably to eliminate the protobuf dependencies from @bazel_tools altogether, but let's make the continuous build green and then think.
*** Original change description ***
Update our rudimentary proto rules to be able to handle gRPC.
--
MOS_MIGRATED_REVID=119271980
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119265313
|
|
|
|
|
|
|
| |
RELNOTES: Enable overriding attributes for Rust binaries.
--
MOS_MIGRATED_REVID=119244456
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixing a few issues with cc_configure that I encountered.
* The argument for rpath should be -Wl,-rpath.
* cc_configure should consider CPLUS_INCLUDE_PATH. I ran into this problem when using
a crosstool gcc which needs -I/usr/include.
* Check if -Wunused-but-set-parameter is available.
--
Change-Id: I73198b5b17674ecbf1b511e23fcc9331ca96c8e0
Reviewed-on: https://bazel-review.googlesource.com/#/c/3210/
MOS_MIGRATED_REVID=118763218
|
|
|
|
|
|
|
| |
Fixes #999
--
MOS_MIGRATED_REVID=118675703
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Static crosstool where copied in the wrong path, leading
to not found package and breaking the Windows build.
Also the BUILD.bazel file contains now a reference
to @cc_configure// package, so we need another copy.
Tested: manually patched the change on the Windows slave and
ran ./compile.sh
Fixes #1101.
--
MOS_MIGRATED_REVID=118674922
|
|
|
|
|
|
|
| |
This is done by adding a default workspace suffix.
--
MOS_MIGRATED_REVID=118656979
|
|
|
|
|
|
|
|
|
| |
it is incorrect.
Currently when you build an app using the built-in rule, the resources compile to google.bazel.R, but the GMS libs need com.google.android.gms.R, so InflateExceptions occur - AdView for one.
--
MOS_MIGRATED_REVID=118204766
|
|
|
|
|
|
|
|
|
|
|
| |
This moves logic out of the Java repository function and closer to where it's
actually used, while also downplaying the basic templating a bit and allowing
the logic to interact better with the build file.
The existing logic regarding Apache's HTTP client is migrated as part of this.
--
MOS_MIGRATED_REVID=118084016
|
|
|
|
|
|
|
| |
Fixes #1043
--
MOS_MIGRATED_REVID=118039426
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117968196
|
|
|
|
|
|
|
| |
RELNOTES: Build the jsonnet tool for the host when cross-compiling.
--
MOS_MIGRATED_REVID=117927673
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117801004
|
|
|
|
|
|
|
|
|
| |
This should reference the //:go_prefix rule in the repository the BUILD file
using go_* is in, not the repository where def.bzl lives (probably
@bazel_tools).
--
MOS_MIGRATED_REVID=117733799
|
|
|
|
|
|
|
|
| |
RELNOTES: Skylark rules that are available from their own repository will now
issue a warning when accessed through @bazel_tools.
--
MOS_MIGRATED_REVID=117730793
|
|
|
|
|
|
|
| |
Adds source files to IosTest runfiles so that mcov/clang has access to them during coverage run.
--
MOS_MIGRATED_REVID=117572134
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117534962
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117478721
|
|
|
|
|
|
|
| |
//third_party/protobuf.
--
MOS_MIGRATED_REVID=117336377
|
|
|
|
|
|
|
| |
RELNOTES: Enable overriding jsonnet binaries and stdlib for Jsonnet rules.
--
MOS_MIGRATED_REVID=117267276
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117258091
|
|
|
|
|
|
|
| |
--
Change-Id: I1831a657552a661a555c7f8bef54e8f46ddd482d
Reviewed-on: https://bazel-review.googlesource.com/#/c/3050/
MOS_MIGRATED_REVID=117238730
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117186609
|
|
|
|
|
|
|
| |
referenced from the crosstool without crossing package boundaries.
--
MOS_MIGRATED_REVID=117137594
|
|
|
|
|
|
|
|
| |
This will avoid confusion with the normal Skylark rule context.
Also fixed indentation of cc_configure.bzl
--
MOS_MIGRATED_REVID=117011107
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116725042
|
|
|
|
|
|
|
| |
This setup was provided on issue #760.
--
MOS_MIGRATED_REVID=116656431
|
|
|
|
|
|
|
|
| |
These tests require exclusive access to the docker daemon
or they sometime fails due to concurrency.
--
MOS_MIGRATED_REVID=116653582
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116593165
|
|
|
|
|
|
|
|
|
|
|
| |
- Skylark does not allow implicit concatenation that was added by the linter
- osx_cc_wrapper renaming was not applied everywhere
- arm toolchain was missing in the toolchain_suite
Also fix the test to use the correct cc_configure.bzl file.
--
MOS_MIGRATED_REVID=116362768
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Version 3.2.1 has a CVSS 10.0 vulnerability. That's the worst kind of
vulnerability that exists. By merely existing on the classpath, this
library causes the Java serialization parser for the entire JVM process
to go from being a state machine to a turing machine. A turing machine
with an exec() function!
https://commons.apache.org/proper/commons-collections/security-reports.html
http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/
--
MOS_MIGRATED_REVID=116309858
|
|
|
|
|
|
|
| |
Fixes #1004.
--
MOS_MIGRATED_REVID=116299622
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116296119
|