| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using this change, changing the target and source version of
//tools/jdk:toolchain, and setting the Java Langtools
(--java_langtools) to a JDK 8 compliant tools.jar, Bazel can
target JDK 7.
A compliant tools.jar to compile with targeting JDK 7 can be found
at http://search.maven.org/#artifactdetails%7Ccom.google.errorprone%7Cjavac%7C1.9.0-dev-r2644-1%7Cjar
--
MOS_MIGRATED_REVID=94591419
|
|
|
|
|
|
|
|
|
|
| |
This is a bit annoying from a UX perspective, as the JDK is an "external
dependency" (and the C++ compiler really should be) so you have to run
"fetch" on new repositories with nothing in the WORKSPACE file before
doing your first build.
--
MOS_MIGRATED_REVID=93532829
|
|
|
|
|
|
|
|
| |
Using JavaBuilder instead of the JDK makes generated jar files
timestampless.
--
MOS_MIGRATED_REVID=89950774
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=88553154
|
|
|
|
|
|
|
|
| |
This should remove the needs for the --cpu=darwin flag under darwin. Bazel build are now using the host cpu too.
This commit also fix the host cpu detection. The host cpu detection was too late and and some corner case was not really working with configurable attributes. It is now done as the default value for the --host_cpu flag.
--
MOS_MIGRATED_REVID=88427551
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=86780976
|
|
--
MOE_MIGRATED_REVID=85702957
|