| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=97675174
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=97334355
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=97258889
|
|
|
|
|
|
|
| |
This stubs out all Android support, but that's okay, because in order to test Android stuff, we need a way to get the NDK and the SDK somehow, which we don't know yet how to do.
--
MOS_MIGRATED_REVID=97222940
|
|
|
|
|
|
|
| |
and aar_generator.sh to the tools directory and make stub applications proper android_library rules instead of stub filegroups.
--
MOS_MIGRATED_REVID=97206853
|
|
|
|
|
|
|
|
| |
This support is based on kchodorow@'s genrule to build the Bazel's dashboard
AppEngine and was tested with it.
--
MOS_MIGRATED_REVID=97135934
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=96883818
|
|
|
|
|
|
|
| |
Fixes #260
--
MOS_MIGRATED_REVID=96806898
|
|
|
|
|
|
|
| |
-client is now the only default JVM options of JavaBuilder
--
MOS_MIGRATED_REVID=96762330
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=96406988
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=96404668
|
|
|
|
|
|
|
|
|
| |
Now that we are using the error-prone javac, there is no need
to impose Java 8. However, because some of our tests are targetting
Java 8, developer should still use a JDK 8 to tests.
--
MOS_MIGRATED_REVID=96400914
|
|
|
|
|
| |
--
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
|
|
|
|
|
|
|
|
|
| |
actually work. This is a temporary measure until these targets are integrated into android_sdk .
Also make handling invalid tools/android/jack packages in JackCompilationHelper a bit more robust.
--
MOS_MIGRATED_REVID=96202009
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Swift sources whitelisted
* Swift compilation and module merging actions
* Swift stdlib copying into IPA action
* Special case for signing embedded swift stdlib dylibs during bundle signing
* Works with mixed ObjC/Swift sources
* Doesn't support working with dependencies from Swift code.
* Requires Xcode 6.3.1 for swift compiler and tooling.
--
MOS_MIGRATED_REVID=96141887
|
|
|
|
|
|
|
| |
Note that despite the rule being present, Android support is still not functional: two tools (//tools/android:{aar_generator,resources_processor} are still missing (and are a-coming!)
--
MOS_MIGRATED_REVID=96099045
|
|
|
|
|
|
|
|
|
| |
The current rule was breaking if jar was not present on the path.
Fixes #245
--
MOS_MIGRATED_REVID=95991168
|
|
|
|
|
|
|
|
|
| |
running system.
Tested on OS X 10.10, Debian 8.1 (x86_64) and Debian 8.1 (i686).
--
MOS_MIGRATED_REVID=95819163
|
|
|
|
|
|
|
|
|
|
|
|
| |
BazelRuleClassProvider:
- Add stub targets to tools/android/BUILD
- Make Constants.ANDROID_DEFAULT_SDK non-constant so that the classfile can be replaced in the .jar
- Make AndroidTools complain if --android_sdk does not point to an android_sdk rule.
- Make the default visibility in the BUILD file generated by android_sdk_repository public
--
MOS_MIGRATED_REVID=95816158
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
I noticed this while testing --split_apk: sometimes APKs would be duplicated on the command line, and simply removing "argv" from "FLAGS(sys.argv + [line.strip()...)" in line 558 would sometimes cause a --adb_arg argument to be lost.
This seems to work for all cases.
--
MOS_MIGRATED_REVID=95715369
|
|
|
|
|
|
|
| |
Fixes #206.
--
MOS_MIGRATED_REVID=95525127
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=95506560
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added target to use java skylark rules to bootstrap
JavaBuilder and SingleJar. Uses thoses target to bootstrap
JavaBuilder and SingleJar and compiles all tools using
Bazel.
--
Change-Id: I5142917c8b31e04015fbab89382df36b4892d8c6
Reviewed-on: https://bazel-review.googlesource.com/#/c/1451/
MOS_MIGRATED_REVID=95281092
|
|
|
|
|
|
|
|
|
|
| |
This magic header marks where --test_output=streamed should start
printing.
Fixes #203.
--
MOS_MIGRATED_REVID=95105573
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=94515805
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=94198797
|
|
|
|
|
|
|
| |
ctx.attr gives the same result.
--
MOS_MIGRATED_REVID=94077958
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
Fixes #67
--
Change-Id: I0d52bcf6f8d5011af545e3d861914fae09a26e42
Reviewed-on: https://bazel-review.googlesource.com/1340
MOS_MIGRATED_REVID=93713804
|
|
|
|
|
|
|
| |
tools/objc/BUILD.
--
MOS_MIGRATED_REVID=93447039
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92725547
|
|
|
|
|
|
|
|
|
|
|
| |
The SDK_VERSION and SIM_DEVICE variables in the runner script had
hard-coded values. This change updates them to be set by the
template expansion, so they can be controlled by the command-line
options.
--
Change-Id: I4a299ee781da19546eb137f115b8c174051ceb5f
MOS_MIGRATED_REVID=92405720
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The SDK_VERSION and SIM_DEVICE variables in the runner script had
hard-coded values. This change updates them to be set by the
template expansion, so they can be controlled by the command-line
options.
--
MOS_MIGRATED_REVID=92278475
--
Change-Id: I4a299ee781da19546eb137f115b8c174051ceb5f
MOS_MIGRATED_REVID=92356562
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
The double quotes are actually incorrect, because the strings we pass in are already single quoted.
*** Original change description ***
Update ios_runner template to dynamically receive options
The SDK_VERSION and SIM_DEVICE variables in the runner script had
hard-coded values. This change updates them to be set by the
template expansion, so they can be controlled by the command-line
options.
--
MOS_MIGRATED_REVID=92337057
|
|
|
|
|
|
|
|
|
|
|
| |
The SDK_VERSION and SIM_DEVICE variables in the runner script had
hard-coded values. This change updates them to be set by the
template expansion, so they can be controlled by the command-line
options.
--
Change-Id: I4a299ee781da19546eb137f115b8c174051ceb5f
MOS_MIGRATED_REVID=92278475
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to my Mac, this is the search path:
Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
#include "..." search starts here:
#include <...> search starts here:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1
/usr/local/include
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/6.0/include
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include
/usr/include
/System/Library/Frameworks (framework directory)
/Library/Frameworks (framework directory)
Fixes #85.
--
MOS_MIGRATED_REVID=91194177
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90612869
|
|
|
|
|
|
|
|
|
|
|
| |
Relative to the last try, add -B to Linux CROSSTOOL entry, and test
the result on OSX and Linux.
This should fix working with GCC cross compilers installed into
/usr/bin/ next to the host ld.
--
MOS_MIGRATED_REVID=90605463
|
|
|
|
|
|
|
|
|
|
| |
This is the patch which fixes the bug reported in #82
https://github.com/google/bazel/issues/82
Change-Id: Ia007b37a3c6156d4373bac24b1776e62d09daa57
--
MOS_MIGRATED_REVID=89992365
|
|
|
|
|
|
|
|
| |
Using JavaBuilder instead of the JDK makes generated jar files
timestampless.
--
MOS_MIGRATED_REVID=89950774
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=89858590
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
OS X does not have rpath so binary fails when not executing
from the good path. This wrapper rewrite the path after the
compilation to fix that behavior.
Fixes #46
--
MOS_MIGRATED_REVID=89527942
|
|
|
|
|
|
|
| |
tool conventions better.
--
MOS_MIGRATED_REVID=89510837
|
|
|
|
|
|
|
| |
Fixes #51
--
MOS_MIGRATED_REVID=89487705
|
|
|
|
|
|
|
|
|
| |
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
|