| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
--
MOS_MIGRATED_REVID=98621744
|
| |
|
|
|
|
|
|
|
|
|
| |
If the system python interpreter is set to python3, some tests fail
because python3 requires parenthesies for the print statement.
Fix this by adding the required parenthesies, which are a no-op for
python2.
--
Reviewed-on: https://github.com/google/bazel/pull/282
MOS_MIGRATED_REVID=97571926
|
| |
|
|
|
| |
--
MOS_MIGRATED_REVID=96572029
|
| |
|
|
|
| |
--
MOS_MIGRATED_REVID=96365813
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Todo:
* Implement rust_bench_test for running benchmarks
* Enable rust_test to depend solely on a rust_library (since many projects
intermix #[test] methods in lib source).
* Improve error checking and handling and prevent rust_binary from directly
depending on cc_library.
* Implement rust_doc for generating rustdoc.
--
MOS_MIGRATED_REVID=96297772
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
Doesn't completely fix but improves #97 for a lot of people.
--
MOS_MIGRATED_REVID=91909946
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
py_test rule enable to use a test written in Python. A py_test is
basically a py_binary that returns a non null on failure. Extraneous
support is need to have nice output (see //src/test/shell/unittest.bash
for the kind of support neeeded).
Actually the py_test code was already there but it was just missing the
necessary glue code. Also added an integration test for py_* rules in
Bazel.
--
MOS_MIGRATED_REVID=91407748
|
| |
|
|
|
|
|
| |
This requires gcc 4.7+ to work, Travis runs gcc 4.6.
--
MOS_MIGRATED_REVID=90818739
|
| |
|
|
|
|
|
|
| |
Add the Google auto generators for Java, for the sake of using AutoValue.
Include dependencies apache commons collections and apache velocity.
--
MOS_MIGRATED_REVID=90482044
|
| |
|
|
|
| |
--
MOS_MIGRATED_REVID=90418845
|
| |
|
|
|
|
|
| |
In particular: add a BazelPythonSemantics implementation and the respective RuleConfiguredTarget factories, rule class definitions and hook them up with BazelRuleClassProvider. Add implicit dependencies (2to3 is just a stub script for now that always fails) and a tiny exampe.
--
MOS_MIGRATED_REVID=89691827
|
| |
|
|
|
| |
--
MOS_MIGRATED_REVID=89513306
|
| |
|
|
|
|
|
| |
tool conventions better.
--
MOS_MIGRATED_REVID=89510837
|
| |
|
|
|
|
|
|
|
| |
It is a first batch of integration tests for Bazel. They tests some
basic behaviors and nominal cases of Bazel rules (especially they tests
the behavior of the examples provided in //examples).
--
MOS_MIGRATED_REVID=89440074
|
|
|
Those examples will be used for Bazel integration tests and their
sources should be available directly to the Bazel workspace itself.
--
MOS_MIGRATED_REVID=89380736
|
Michael Thvedt
David Chen
Carmi Grushko
Damien Martin-Guillerez
Lukacs Berki
Steven Dee
Francois-Rene Rideau
John Field
Alex Humesky
Peter Foley
Nathan Harmata
Liam Miller-Cushon
Han-Wen Nienhuys
Kristina Chodorow
Daniel Wagner-Hall