aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/BUILD
Commit message (Collapse)AuthorAge
* Moving the RemoteWorker into tools/remote directory.Gravatar olaola2017-12-05
| | | | | | | | This is because I want to add another remote execution related tool, the remote_client, which will use the Remote Execution API to fetch blobs from a remote cache. I will use this tool as part of end-to-end tests for remote execution. TESTED=remote integration tests, presubmit RELNOTES: None PiperOrigin-RevId: 177995895
* Move bazel conditions into src/conditions.Gravatar tomlu2017-11-30
| | | | | | | This will enable an easier transition from checked-in BUILD files to ones generated by copybara. RELNOTES: None PiperOrigin-RevId: 177514519
* Add //tools/jdk:current_java_runtime / tools/jdk:current_host_java_runtime ↵Gravatar lberki2017-11-24
| | | | | | | | | | | to rules that use the $(JAVA) or the $(JAVABASE) Make variable. This is necessary because a future Blaze version will require this for rules that use said Make variables. This incompatible change can be tested today by adding the --noexperimental_enable_jvm_configuration_make_variables command line option to Blaze. This change is part of a large-scale change ([] RELNOTES: None. PiperOrigin-RevId: 176834987
* Add test to monitor dependency change of //src:embedded_tools_srcs.Gravatar xingao2017-11-06
| | | | PiperOrigin-RevId: 174482602
* Delete benchmark code.Gravatar tomlu2017-11-06
| | | | | | This is no longer maintained and the CI is turned down. PiperOrigin-RevId: 174456265
* Enable switching singlejar and ijar targets for remote execution.Gravatar xingao2017-11-02
| | | | | | When --define EXECUTOR=remote is specified in bazel command, embedded tool singlejar and ijar will be compiled remotely from source. PiperOrigin-RevId: 174195094
* shell,runfiles: add runfiles libraryGravatar Laszlo Csomor2017-10-11
| | | | | | | | | | | | Create sourceable runfiles.sh that implements rlocation and a couple other helper functions for shell scripts. Change-Id: Ifcf9ee86ed63afe2ce655be596ac781494660398 RELNOTES[NEW]: runfiles, sh: Shell scripts may now depend on //src/tools/runfiles:runfiles_sh_lib and source runfiles.sh. The script defines the `rlocation` function which returns runfile paths on every platform. PiperOrigin-RevId: 171816037
* Use bundled proguard 5.3.3 instead of 4.7 from the SDKGravatar ajmichael2017-10-06
| | | | | | | | | Fixes https://github.com/bazelbuild/bazel/issues/3777 Also adds a proguard integration test so that hopefully we notice next time it breaks. RELNOTES: Updated Android proguard to 5.3.3. It now works with android-24+. PiperOrigin-RevId: 171162295
* Remove client (or client.exe) from the Bazel self-extracting zip.Gravatar lberki2017-09-29
| | | | | | | The same binary is *outside* of the zip so there is no point in repeating it. RELNOTES: None. PiperOrigin-RevId: 170461181
* Remove unncessary duplication of zipper target.Gravatar xingao2017-09-22
| | | | PiperOrigin-RevId: 169563077
* CI,Windows: run //third_party/def_parser testsGravatar László Csomor2017-09-22
| | | | | | | Fixes https://github.com/bazelbuild/bazel/issues/3742 Change-Id: Ibfa1909e387e9734040b00523cc9388a386e0bf4 PiperOrigin-RevId: 169538023
* CI,windows: create test_suites for Windows testsGravatar L?szl? Csomor2017-09-19
| | | | | | | | | | | | | | | Add recursive test_suite rules for all tests that ci.bazel.io runs for Windows, and set the top-level test_suite as the CI test target. Doing so shortens the command line and works around https://github.com/bazelbuild/bazel/issues/3742 I verified that the old set of tests are the same as the new set. Change-Id: Id8d5da3f0c03c9b8969a9f8e1e9a3096888365aa PiperOrigin-RevId: 169242858
* Bazel now can build dynamic library from cc_libraryGravatar Yun Peng2017-09-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Working towards: https://github.com/bazelbuild/bazel/issues/3311 When building dynamic library on Windows, Bazel builds an import library and a DLL. Bazel provides a feature called windows_export_all_symbols, if this feature is enabled(and no_windows_export_all_symbols is not) for a cc_library, then Bazel parses object files of that cc_library to generate a DEF file that will be used during linking time to export symbols from DLL. This feature can be specified at crosstool, package, target and command line level. A few differences from Unix platforms: 1. We don't build the shared library on Windows by default, users have to specifiy --output_groups=dynamic_library for building dynamic libraries. This output group is also available on other platforms. 2. By default, cc_test is dynamically linked on Unix, but it will be statically linked on Windows by default. (meaning the default value of linkstatic in cc_test is 1 on Windows, and 0 on other platforms) 3. For global data symbols, __declspec(dllimport) must still be used in source files. Remaining issues: 1. Extensions for import library and DLL are not correct yet. 2. DLLs are not guaranteed to be available during runtime yet. 3. Diamond problem If a cc_library A is specified as linkstatic=0, then no dynamic library will be built for it, so if another cc_library B depends on it, A will be statically linked into B, and if a cc_binary C depends on B, A will also be statically linked into C and B will be dynamically linked to C. This is wrong because A is duplicated in both B and C. It is essentially a diamond problem describled in C++ Transitive Library. (https://docs.google.com/document/d/1-tv0_79zGyBoDmaP_pYWaBVUwHUteLpAs90_rUl-VY8/edit?usp=sharing) Hopefully, we can avoid this by using cc_shared_library rule in future. Change-Id: I23640d4caf8afe65d60b1522af6368536d7a8408 PiperOrigin-RevId: 168829958
* Automated rollback of commit 72de1fe6bafa28fddcbc8cdc1ccbb59556996bfb.Gravatar dmarting2017-09-13
| | | | | | | | | | | | | | | | | | | | | | | *** Reason for rollback *** Roll-forward with fix *** Original change description *** Automated rollback of commit f5b8281f1f7599c67476663887db909a4206710e. *** Reason for rollback *** Read the wrong log, it is not timing out, actual failure. *** Original change description *** Open-source src/test/skylark/... This was means to be open-sourced from the beginning but an error in our set-up hide it from the open-source tree. PiperOrigin-RevId: 168526758
* Automated rollback of commit f5b8281f1f7599c67476663887db909a4206710e.Gravatar dmarting2017-09-13
| | | | | | | | | | | | | | | *** Reason for rollback *** Read the wrong log, it is not timing out, actual failure. *** Original change description *** Open-source src/test/skylark/... This was means to be open-sourced from the beginning but an error in our set-up hide it from the open-source tree. PiperOrigin-RevId: 168428572
* Open-source src/test/skylark/...Gravatar dmarting2017-09-13
| | | | | | | This was means to be open-sourced from the beginning but an error in our set-up hide it from the open-source tree. PiperOrigin-RevId: 168427396
* More BUILD file refactorings.Gravatar philwo2017-09-06
| | | | | | | | | Split collect, concurrent, vfs, windows into package-level BUILD files. Move clock classes out of "util", into their own Java package. Move CompactHashSet into its own Java package to break a dependency cycle. Give nestedset and inmemoryfs their own package-level BUILD files. PiperOrigin-RevId: 167702127
* Remove some left over bits of Java 7 supportGravatar Liam Miller-Cushon2017-09-04
| | | | | Change-Id: I3fce66ec2e63d152aafc0cf9ea067d6dbf1245f7 PiperOrigin-RevId: 167484075
* Auto-generate BUILD files for src/java_tools/junitrunnerGravatar ulfjack2017-08-28
| | | | | | | | | This and further changes may contain minor modifications to BUILD files that don't serve any apparent purpose. The reason for these changes is that we're switching from checked-in BUILD files to generated BUILD files, and there may be small differences between these files. PiperOrigin-RevId: 166684362
* Busybox all the Bazel Android tools.Gravatar ajmichael2017-08-25
| | | | | | | | | This change reduces the size taken up in the bazel binary by Android tools deploy jars from 38.2 mb to 9.8 mb, which is 15% of the bazel binary size. Also, some minor cleanups of our BUILD files. https://github.com/bazelbuild/bazel/issues/2385 RELNOTES: None PiperOrigin-RevId: 166373241
* Start work on the Skylark linter (skylint).Gravatar fzaiser2017-08-23
| | | | | | | | This commit introduces checking of naming conventions, i.e. upper and lower snake case. RELNOTES: None PiperOrigin-RevId: 166073284
* Rewrite //:combine_distfiles.sh in PythonGravatar László Csomor2017-08-11
| | | | | | | | | | | | | | | | It can only pack to zip for now (packing to tar is not trivial and I haven't figured it out yet). This allows building //:bazel-distfile on Windows. Previously it was either timing out or taking so long that it was unbearable (over 10 minutes). I never waited long enough to see it build. The new Python version runs under just a few seconds. Change-Id: I3264eb7132dd58c581c4216e5bbab035a79d716d PiperOrigin-RevId: 164954162
* Extract a library from create_embedded_tools.pyGravatar László Csomor2017-08-11
| | | | | | | | | We'll use the extracted functions in the upcoming Python-based reincarnation of the //:bazel-distfile rule. Change-Id: I5140938ae4af50f62fb695b5b96cd41f3cd939ef PiperOrigin-RevId: 164950515
* Remove old intellij aspect code bundled with BazelGravatar Googler2017-07-31
| | | | PiperOrigin-RevId: 163538636
* Apply native binary launcher to sh_binaryGravatar Yun Peng2017-07-31
| | | | | | | | | | | | This change: 1. Added launcher to @bazel_tools If the host platform is Windows, we use a prebuilt launcher.exe , otherwise the launcher needs to be built with MSVC first. 2. Launching sh_binary using native launcher. Change-Id: I5a63135455057fbfe04ff0cce7ec7994ef0c347a PiperOrigin-RevId: 163442540
* Replace create_embedded_tools.sh with a faster Python version.Gravatar Philipp Wollermann2017-07-28
| | | | | | | | | This is functionally equivalent, but ~30x faster on Windows, ~2x faster on macOS and ~1.5x faster on Linux. RELNOTES: None. Change-Id: Ib4a7e10400a3955e47772425acfce2d9530de462 PiperOrigin-RevId: 163346634
* Remove generate_workspace from BazelGravatar kchodorow2017-07-25
| | | | | | | It now exists as a separate project at https://github.com/bazelbuild/migration-tooling. PiperOrigin-RevId: 162970509
* Stops ARM from compiling 64-bit only C++ SingleJar ↵Gravatar Alois Klink2017-07-24
| | | | | | | | | | (https://github.com/bazelbuild/bazel/blob/master/tools/cpp/lib_cc_configure.bzl#L106-L107)), forcing bazel to use the `SingleJar_deploy.jar` java implementation of SingleJar fixes this issue. I suspect 32-bit Unix has the same issue, which could be fixed by adding the same configuration for `piii`, but I don't have a 32-bit x86 system to test it on. But if anyone is here by Googling the above error code, try replacing all the `arm` references in this pull request with `piii`! Closes #3382. PiperOrigin-RevId: 162923371
* Windows: Implement native binary launcherGravatar Yun Peng2017-07-24
| | | | | | | | The native launcher is implemented based on this design doc: https://docs.google.com/document/d/1z6Xv95CJYNYNYylcRklA6xBeesNLc54dqXfri0z0e14/edit?usp=sharing Change-Id: I83bae844f792a587ce0e342a3c0f238b760afeaa PiperOrigin-RevId: 162736269
* Add //third_party/py/six to embedded_tools.Gravatar Joe Finney2017-07-19
| | | | | | | | | https://github.com/bazelbuild/bazel/pull/3363#issuecomment-314774384 Closes #3369. Change-Id: I52c7c39db13131bfc343666fbd05840815ee7fa8 PiperOrigin-RevId: 162478002
* build_windows_jni.sh: move file to subdirectoryGravatar Laszlo Csomor2017-07-05
| | | | | | | | | | | | | The script more logically belongs in src/main/native/windows than in src/main/native. Also move the //src/main/native:windows_jni rule into //src/main/native/windows:windows_jni, so the logic of building the JNI library is fully contained in that package. Change-Id: I96e19003932cc0ddc5af3471b0b31a1aec09b8fa PiperOrigin-RevId: 160876594
* //src:derived_java_srcs: use jar from JAVABASE instead of PATHGravatar Klaus Aehlig2017-07-03
| | | | | | | | | | The genrule //src:derived_java_srcs so far assumed to find the needed tool jar(1) on PATH. This, however, is not true in all setups. Instead, use jar from JAVABASE, which should be the correct toolchain to be used on the execution platform. Fixes #3284. Change-Id: I1f972f819786b511237c448a6c57484a76f4118b PiperOrigin-RevId: 160634222
* Add missing windows select for //src:embeded_tools_with_jdkGravatar pcloudy2017-06-29
| | | | | | | | Fix the failure at http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/PLATFORM_NAME=windows-msvc-x86_64/1620/console RELNOTES: None. PiperOrigin-RevId: 160504102
* Move the docker tests in src/test/dockerGravatar dmarting2017-06-27
| | | | | | | | | | | | This is a better location and tools/cpp is packaged in embedded_tools that make the test ends-up in embedded_tools, which is requiring network access to build embedded_tools! Side-effect: have to correctly mock the bazel workspace file on a couple of tests. This is blocking on https://bazel-review.googlesource.com/c/12350/ PiperOrigin-RevId: 160265524
* Remove remaining xcodegen references.Gravatar schmitt2017-06-26
| | | | | | | Deletes last code references to xcodegen tool as well as tool itself. RELNOTES: None. PiperOrigin-RevId: 160137807
* Make source code of singlejar and ijar available from @bazel_tools. ,Gravatar Xin Gao2017-06-22
| | | | | | | | | | Please refer to patch set 9 and its CI run for usage and test results. In practice, users should create their own java_toolchain rule in their project's BUILD file, and set the two attributes like above instead of modifying //tools/jdk/BUILD. Change-Id: Ic880f243086b00a58d453a8139ba4c957fe54bc7 PiperOrigin-RevId: 159694649
* Make singlejar aware of FreeBSDGravatar Klaus Aehlig2017-06-09
| | | | | | | | | | | | | The C implementation of singlejar verifies that it is built for a supported system; currently those are 64-bit linux and apple systems. However, the code is portable enough that it can easily be adapted to run on 64-bit FreeBSD systems as well. In fact, only the path of a single header file is different, and we need to link with -lm. Fixes #3096. Change-Id: Id69542ad940f1161aceb55eb8f5dabda2f486747 PiperOrigin-RevId: 158533955
* Testing: add Python integration test utilitiesGravatar Laszlo Csomor2017-06-09
| | | | | | | | | | | | | | This allows writing integration tests in Python rather than shell, so we can avoid https://github.com/bazelbuild/bazel/issues/3148 This change also adds a test to verify that running "bazel info server_pid" twice yields the same PID. Again, this is testing that we indeed avoid the aformentioned bug. Change-Id: Ic800965b16ab87179370fd2cd43908286120e8d5 PiperOrigin-RevId: 158517192
* Use generated third_party/googleapis java sources for boostrapping.Gravatar Jakob Buchgraber2017-06-09
| | | | | Change-Id: I9652195e3f8d6f7912a1c52880f23114d34c6ebf PiperOrigin-RevId: 158439371
* Automated g4 rollback of commit dba22f337a20d3e8f3ac8dfd23bc6fa69e4528da.Gravatar xingao2017-06-02
| | | | | | | | | | | | | | | | | | | | | *** Reason for rollback *** Use Java implementation of singlejar on FreeBSD, and roll forward change 157473007. *** Original change description *** Automated g4 rollback of commit d894345ed88f8adce600b66a310b5210d0bcb59c. *** Reason for rollback *** Breaks Bazel on FreeBSD: http://ci.bazel.io/view/Dashboard/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=freebsd-11/1542/console *** Original change description *** Use cc implementation of singlejar except on Windows. Change-Id: Ie4a2db2a6fa1ea86f4bdd42cd806f6804a0c56d4 PiperOrigin-RevId: 157729503
* Automated g4 rollback of commit d894345ed88f8adce600b66a310b5210d0bcb59c.Gravatar laszlocsomor2017-05-31
| | | | | | | | | | | | | *** Reason for rollback *** Breaks Bazel on FreeBSD: http://ci.bazel.io/view/Dashboard/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=freebsd-11/1542/console *** Original change description *** Use cc implementation of singlejar except on Windows. Change-Id: Ie4a2db2a6fa1ea86f4bdd42cd806f6804a0c56d4 PiperOrigin-RevId: 157567871
* Adds external J2ObjC BUILD files to Bazel's generated embedded_tools directory,Gravatar Googler2017-05-31
| | | | | | | and fixes some of J2ObjC's implicit deps to correctly reference the embedded tools. RELNOTES: Partially fixes external J2ObjC support. PiperOrigin-RevId: 157503022
* Use cc implementation of singlejar except on Windows.Gravatar Xin Gao2017-05-31
| | | | | Change-Id: Ie4a2db2a6fa1ea86f4bdd42cd806f6804a0c56d4 PiperOrigin-RevId: 157473007
* Select correct JDK for windows_msysGravatar dslomov2017-05-16
| | | | | RELNOTES: None. PiperOrigin-RevId: 156113782
* add config setting for LinuxGravatar Thiago Farina2017-05-15
| | | | | | | | | That way we can detect Linux and use it in select(). I would like to use as part of https://bazel-review.googlesource.com/10490 Change-Id: Ifa88626e906a52af55ec8e85139b8223b556382f PiperOrigin-RevId: 155868359
* Migrate off versioned javac and Error Prone targetsGravatar Liam Miller-Cushon2017-05-09
| | | | | Change-Id: Iad1e07ad55d5304d7c3dbb8bdab856728a91432d PiperOrigin-RevId: 155375893
* Update to javac9-r4023Gravatar cushon2017-04-25
| | | | PiperOrigin-RevId: 154078281
* Embed a prebuilt jarjar into Bazel so that Android builds work again.Gravatar lberki2017-04-20
| | | | | | | Fixes #2848. RELNOTES: None. PiperOrigin-RevId: 153692641
* Stop embedding apkbuildermain in Bazel binary.Gravatar ajmichael2017-04-14
| | | | | | | | | | | It is no longer used since --use_singlejar_apkbuilder is the default. A future change will remove apkbuildermain from the Bazel codebase. 4MB bazel binary size savings! :) RELNOTES: None PiperOrigin-RevId: 153079733
* Move xcrunwrapper and libtool to third_party/bazel/tools/objc from their ↵Gravatar cparsons2017-04-14
| | | | | | | | | xcode src directories There's no value in having these copied over from src/tools to tools/objc separately. RELNOTES: None. PiperOrigin-RevId: 153060955
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-02 01:26:44 +0000