| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
| |
run following commands to test it:
bazel build --cpu=x64_windows_msvc examples/windows/dll:hello
./bazel-bin/examples/windows/dll/hello
--
Change-Id: I096f6ff66473b1c9980b0aa36ec291f39512dd71
Reviewed-on: https://bazel-review.googlesource.com/#/c/3932
MOS_MIGRATED_REVID=126300284
|
|
|
|
|
|
|
|
|
|
| |
bazel test now works for java native example tests, but most of
Bazel's java_test still fail on Windows due to other reasons.
--
Change-Id: Ie4ab6570b294815b9e06dd9bbd0cb7a48eb6ed11
Reviewed-on: https://bazel-review.googlesource.com/#/c/3810
MOS_MIGRATED_REVID=124932604
|
|
|
|
|
|
|
| |
Discovered while discussing #1321
--
MOS_MIGRATED_REVID=123946533
|
|
|
|
|
|
|
|
| |
* Modules are now named after its full target path by default.
* module_name attribute can be used to override this logic.
--
MOS_MIGRATED_REVID=123422704
|
|
|
|
|
|
|
|
| |
Those rules were moved to, respectively, https://github.com/bazelbuild/rules_rust,
https://github.com/bazelbuild/rules_jsonnet, https://github.com/bazelbuild/rules_scala, and https://github.com/bazelbuild/rules_closure.
--
MOS_MIGRATED_REVID=121834063
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES: Bazel's workspace name is now io_bazel. If you are using Bazel's
source as an external repository, then you may want to update the name you're
referring to it as or you'll begin seeing warnings about name mismatches in your
code.
--
MOS_MIGRATED_REVID=120926179
|
|
|
|
|
|
|
|
| |
* Adds a swift_library rule that produces a (.a, .swiftmodule) pair. It can handle dependencies between modules and can be used as a dependency of objc_binary.
* Does not work with Objective-C yet.
--
MOS_MIGRATED_REVID=120578875
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 790d2f6009d47fe92cf0cd92a1473bbf0141f32e.
*** Reason for rollback ***
Broke non-Bazel projects on ci.bazel.io
Fixes #1168
*** Original change description ***
Move the runfiles for external repositories to under the x.runfiles/ directory
This also sets the Bazel workspace name to io_bazel_source.
Fixes #848.
Relevant to #1116, #1124,
RELNOTES[INC]: All repositories are now directly under the x.runfiles directory in the runfiles tree (previously, external repositories were at x.runfiles/main-repo/external/other-repo. This simplifies handling remote repository runfiles considerably, but will break existing references to external repository runfiles....
***
--
MOS_MIGRATED_REVID=120535721
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also sets the Bazel workspace name to io_bazel_source.
Fixes #848.
Relevant to #1116, #1124,
RELNOTES[INC]: All repositories are now directly under the x.runfiles directory in the runfiles tree (previously, external repositories were at x.runfiles/main-repo/external/other-repo. This simplifies handling remote repository runfiles considerably, but will break existing references to external repository runfiles.
---
Furthermore, if a Bazel project does not provide a workspace name in the WORKSPACE file, Bazel will now default to using __main__ as the workspace name (instead of "", as previously). The repository's runfiles will appear under x.runfiles/__main__/.
--
MOS_MIGRATED_REVID=120224534
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117968196
|
|
|
|
|
|
|
| |
Will need to release before we can remove resources from objcbinary rules.
--
MOS_MIGRATED_REVID=116571890
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116272974
|
|
|
|
|
|
|
| |
update instructions on how to generate.
--
MOS_MIGRATED_REVID=115175144
|
|
|
|
|
|
|
|
| |
RELNOTES[INC]: Renamed proto_java_library to java_proto_library. The former
is now deprecated and will print out a warning when used.
--
MOS_MIGRATED_REVID=115012027
|
|
|
|
|
|
|
|
|
| |
This is in preparation for another change that will add a new helper script
to the tools/build_rules directory, and such script requires a BUILD rule
of its own.
--
MOS_MIGRATED_REVID=114898083
|
|
|
|
|
|
|
| |
Python sources filegroup was broken by the addition of a new package
--
MOS_MIGRATED_REVID=114323099
|
|
|
|
|
|
|
|
|
|
|
| |
directories to PYTHONPATH.
Fixes #702
RELNOTES: Add imports attribute to native Python rules.
--
MOS_MIGRATED_REVID=114314430
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=113789897
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=113782855
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will fix some issue with loading skylark rules from @bazel_tools.
Tested with ./compile.sh all and also a project that use pkg_tar from
@bazel_tools (which is broken at HEAD).
--
Change-Id: Iffbb7134ef5fee497890c4d01b85084973d45ad0
Reviewed-on: https://bazel-review.googlesource.com/2800
MOS_MIGRATED_REVID=113508661
|
|
|
|
|
|
|
|
|
| |
instead of just objc_binary.
RELNOTES:
--
MOS_MIGRATED_REVID=112601304
|
|
|
|
|
|
|
|
|
| |
RELNOTES[NEW]: A new java test runner that support XML output and test filtering is supported.
It can be used by specifying --nolegacy_bazel_java_test or by speicifying the test_class
attribute on a java_test.
--
MOS_MIGRATED_REVID=112028955
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix conflicting .deps directory creation by rust_test rule
* Fix dependency symlinking in generated rust_doc_test scripts
Fixes #572
TESTED: bazel test //examples/rust/...
--
MOS_MIGRATED_REVID=108617330
|
|
|
|
|
|
|
|
|
| |
Adds rules for csharp_binary, csharp_library, and csharp_nunit_test.
--
Change-Id: I51e448a399c535554353b3f40bf090bb602f647f
Reviewed-on: https://bazel-review.googlesource.com/#/c/2270/
MOS_MIGRATED_REVID=107399181
|
|
|
|
|
|
|
| |
sandboxing was enabled, by adding "jni_dep.h" to "hdrs" in //examples/android/java/bazel:jni_dep.
--
MOS_MIGRATED_REVID=106408122
|
|
|
|
|
|
|
| |
RELNOTES: [jsonnet] Add jsonnet_to_json_test rule for testing Jsonnet code.
--
MOS_MIGRATED_REVID=106040951
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105949508
|
|
|
|
|
|
|
|
| |
bazel test examples/go/lib:lib_test
bazel build examples/go/bin:bin
--
MOS_MIGRATED_REVID=105070940
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rust_test rule.
* Add rust_bench_test rule to run benchmark tests
* Add rust_doc_test rule to run Rust documentation tests.
* Enable rust_test and rust_bench_test to depend directly on a rust_library target.
* Rename rust_docs rule to rust_doc for consistency.
RELNOTES: [rust] Add rust_bench_test and rust_doc_test rules and improve usability of rust_test tule.
--
MOS_MIGRATED_REVID=104648497
|
|
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
|
|
|
|
|
|
|
|
|
|
|
| |
Additional updates to Rust rules:
* Consolidate BUILD files for Rust distribution.
* Prevent rust_binary from depending directly on cc_library.
* Update Rust version to 1.3.0
RELNOTES: [rust] Add rust_docs rule for generating rustdoc.
--
MOS_MIGRATED_REVID=103827592
|
|
|
|
|
|
|
|
|
| |
RELNOTES[NEW]: Support for build with libsass.
--
Change-Id: I2a24212d9466e2e2a8b653027f1cc9579b4d4221
Reviewed-on: https://bazel-review.googlesource.com/#/c/1990/
MOS_MIGRATED_REVID=103740130
|
|
|
|
|
|
|
|
|
| |
d_source_library.
RELNOTES: [d] d_docs rules now depend on a d_binary, a d_library or d_source_library.
--
MOS_MIGRATED_REVID=103736167
|
|
|
|
|
|
|
| |
objc_proto_library with native proto_library.
--
MOS_MIGRATED_REVID=102962083
|
|
|
|
|
|
|
| |
RELNOTES: Add Jsonnet rules to Bazel
--
MOS_MIGRATED_REVID=102895524
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102513092
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102299629
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102294703
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is not really nice, there are several hacks there. This
repository will get removed in the future and linked to a
remote one instead. I tested it against the tutorial and
it works like a charm. mobile-install seems like to work,
maybe that's also fixing the last issue reported in #392.
Known issue: Java compilation output errors about files being
modified in the future.
--
MOS_MIGRATED_REVID=102282979
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that Bazel finds Android tools and update the tools themselves to handle their new location.
This paves the way for eventually referencing every tool this way.
We have to figure out if android_http_tools_repository is the right way to distribute the Android tools, but now that we don't have a binary distribution yet, it's not an immediate problem.
This will break existing users of Android support in Bazel, whom I'll inform over bazel-discuss.
Fixes #384.
--
MOS_MIGRATED_REVID=101456190
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101446590
|
|
|
|
|
|
|
| |
and add an example.
--
MOS_MIGRATED_REVID=100493818
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Make the jni target depend on another cc_library.
- Disable legacy native support in hello_world.
- Make MainActivity load hello_world rather than jni.
--
Change-Id: I497ba680eec4e16ee14628294d2c1260db69ad82
Reviewed-on: https://bazel-review.googlesource.com/#/c/1740/
MOS_MIGRATED_REVID=99709707
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99464781
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99378104
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=99179050
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=98856262
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=98640520
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in the WORKSPACE file.
The error reporting if an android_ndk_repository rule is present is not very user-friendly (it just uses the non-Android toolchain, resulting in compile errors) but given that --android_crosstool_top is an interim solution until we get reasonable multi-platform support, I suppose it's fine.
As a side effect, instead of prefixing fat APK output directories with "fat-apk-", we prefix Android output directories with "android-".
This makes it possible to build Android apps with zero command line options. Rejoice!
--
MOS_MIGRATED_REVID=98624120
|