aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/main/tools/jdk.BUILD
Commit message (Collapse)AuthorAge
* Add runfiles in jdk.BUILDGravatar Stephen Twigg2017-04-06
| | | | | | | | | | | | | | | | | | | | | Add jdk as runfiles for java, jar, and javac in jdk.BUILD. Done via data attribute of filegroup. This should 'mostly' work if you handwave around the differences between default_runfiles and data_runfiles. The jdk runfiles will always be accessed via data_runfiles, and thus not platform-targeted. Therefore, my expectation is the target machine will be sent the host JDK. However, since the jdk is itself composed of binary imports anyway, it seems like the JDK already has issues being platform-targeted. To reviewers: I didn't do a thorough audit of the jdk.BUILD file. More specifically, unsure if xjc or wsimport need a jdk as well. Still investigating a good testing strategy. Change-Id: I138b95b8cee2808c89e4202b822ada6a6577acce PiperOrigin-RevId: 152290935
* Make MSVC CROSSTOOL default on Windows Gravatar Yun Peng2017-03-08
| | | | | | | | | | | | | | | | The default C++ CROSSTOOL on Windows now becomes MSVC, --cpu=x64_windows_msvc is still supported To use MSYS toolcahin, add --cpu=x64_windows_msys and --host_cpu=x64_windows_msys for host compilation See https://github.com/bazelbuild/bazel/issues/2627 -- Change-Id: Ie788a39cb5ffbc9fc956ccfd51a3cc816c74543a Reviewed-on: https://cr.bazel.build/9292 PiperOrigin-RevId: 149530250 MOS_MIGRATED_REVID=149530250
* Windows: Assist JNI builds with a target for jni_md.h. Gravatar Asim Shankar2017-03-08
| | | | | | | | | | | | | This rule can be used in building JNI shared libraries for Windows. For example, see TensorFlow usage of these targets in jdk.BUILD: https://github.com/tensorflow/tensorflow/blo[]a98083a6c16f263d668271889863596efbeb84/tensorflow/java/src/main/native/BUILD#L68 Closes #2599. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/2599 PiperOrigin-RevId: 149527656 MOS_MIGRATED_REVID=149527656
* Rename 'extdir' to 'extclasspath'Gravatar Liam Miller-Cushon2017-02-17
| | | | | | | | | The targets contain the entries in the extdir and are used to construct a classpath, so the label is not actually a directory. -- PiperOrigin-RevId: 147798672 MOS_MIGRATED_REVID=147798672
* Migrate to java_runtime{,_suite}Gravatar Liam Miller-Cushon2017-02-17
| | | | | | -- PiperOrigin-RevId: 147727032 MOS_MIGRATED_REVID=147727032
* Remove JavaCpuSupplier; use the actual --cpu value instead.Gravatar Ulf Adams2016-10-06
| | | | | | | | | | | | This is a semantic change for Bazel, which now observes the --cpu flag when looking up a Jvm. Use "-default" as a fallback to keep the change backwards compatible. RELNOTES[INC]: Bazel now uses the --cpu flag to look up Jvms; it falls back to "default" if it can't find a Jvm matching the CPU value. -- MOS_MIGRATED_REVID=135333759
* Fixes bugs so that we can build bazel with bazel on WindowsGravatar Yun Peng2016-04-14
| | | | | | | | | | | | | | | | | | | src/main/java/com/google/devtools/build/lib/exec/SymlinkTreeHelper.java: enable --windows_compatible flag on Windows to make build-runfiles.exe work. scritps/bootstrap/compile.sh: --windows_compatible will also be passed to a dummy build-runfiles.exe defined in complie.sh. Which is actully a batch script, modify it to make it work. ----- With the changes above, we are able to build bazel with bazel. But when you try to run ./compile.sh compile /path/to/bazel again without clean up tmp directory, it will fail with a permission deny error. The reason seems to be that you can't use build-runfile.exe to build the same hard link twice, still trying to solve that. -- Change-Id: I93340b1ba9fa415f6db963b106e264799e33ede3 Reviewed-on: https://bazel-review.googlesource.com/#/c/3334 MOS_MIGRATED_REVID=119751076
* Exclude weirdly-named files from the JDK.Gravatar Lukacs Berki2016-02-24
| | | | | | | This remotes one stumbling block from bootstrapping on Windows. -- MOS_MIGRATED_REVID=115447112
* Fix JDK tools extensions for Windows.Gravatar Dmitry Lomov2016-02-12
| | | | | | | Needed for #276. -- MOS_MIGRATED_REVID=114527619
* Export xjc and wsimport tools from JDKGravatar Alpha Lam2015-12-02
| | | | | | | | | | | This change exports //tools/jdk:xjc and //tools/jdk:wsimport as external tools. This will allow build rules to generate JAXB and JAX-WS artifacts. -- Change-Id: I6e2cf5a155be5070c346421302ad96b3e1c2188c Reviewed-on: https://bazel-review.googlesource.com/#/c/2420 MOS_MIGRATED_REVID=109172989
* Port to FreeBSD.Gravatar Doug Rabson2015-08-26
| | | | | | | -- Change-Id: I4e65cc583e758d2f7e45209ffcb37f6a871e2ed7 Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1840 MOS_MIGRATED_REVID=101462155
* Improve the JDK and JRE filegroups to include all the necessary parts. Then ↵Gravatar Philipp Wollermann2015-08-24
| | | | | | | fix the Skylark rules and tests that so far failed to declare dependencies on the JVM. -- MOS_MIGRATED_REVID=101215495
* Reintroduce langtools and langtools-neverlink in jdk.BUILDGravatar Damien Martin-Guillerez2015-06-19
| | | | | | | | Removing them would break people that have their tools folder checked in their workspace. -- MOS_MIGRATED_REVID=96392423
* Move the Error Prone plugin into BazelGravatar Liam Miller-Cushon2015-06-19
| | | | | -- MOS_MIGRATED_REVID=96365813
* Remove tools/jdk/jdk symbolic link creationGravatar Damien Martin-Guillerez2015-06-11
| | | | | | | | | | Skylark rules now depends completely on the external repository to access the JDK tooling. -- Change-Id: I48d461524d63d556bcd4af49f6ba2aecf1ed7068 Reviewed-on: https://bazel-review.googlesource.com/#/c/1500/ MOS_MIGRATED_REVID=95720688
* Simplify genproto.bzl.Gravatar Han-Wen Nienhuys2015-06-02
| | | | | | | | | | | | | | | | Generate a srcjar artifact, and use native.java_library to emit the actual jar file. Post-review modifications: - Formatted genproto.bzl - Use //external:jar instead of relying on PATH - Make proto library a java_import instead of a filegroup in test setup. -- Change-Id: I005f801f09439bbca43e483ad4a47da4588fea94 Reviewed-on: https://bazel-review.googlesource.com/1362 MOS_MIGRATED_REVID=94914935
* Add a --javac_extdir flag to enable configuring the javac -extdirs flagGravatar Liam Miller-Cushon2015-05-21
| | | | | | | | | | | | | The -extdirs flag sets a search path to the directory containing the JDK's extension classes, and should always be set explicitly when cross-compiling. If it is unset, the ext directory of the host JDK will be used instead. javac requires that -extdirs be a list of directories. The blaze --javac_extdir flag takes the label of a filegroup with the 'path' attribute set, and passes the directory path through to JavaBuilder. -- MOS_MIGRATED_REVID=94001278
* Make JDK not need tools/jdk/jdk symlinkedGravatar Kristina Chodorow2015-03-18
-- MOS_MIGRATED_REVID=88742425
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-28 05:49:36 +0000