aboutsummaryrefslogtreecommitdiffhomepage
path: root/examples/android
Commit message (Collapse)AuthorAge
* Update the Bazel sample app to demonstrate the support library syntax.Gravatar Adam Michael2016-12-22
| | | | | | | | Also removes some outdated comments in the README.md. -- PiperOrigin-RevId: 142705870 MOS_MIGRATED_REVID=142705870
* Add all the sources to //:srcs filegroup and add a check to detectGravatar Damien Martin-Guillerez2016-07-01
| | | | | | | | | | | missing file to it. We need to activate this check on presubmits -- Change-Id: Ia95e92d3816ce92bb69bc0e2cf56e9c60b68d970 Reviewed-on: https://bazel-review.googlesource.com/#/c/3949/ MOS_MIGRATED_REVID=126404792
* Fixes compilation failure of //examples/android/java/bazel:hello_world when ↵Gravatar Philipp Wollermann2015-10-27
| | | | | | | sandboxing was enabled, by adding "jni_dep.h" to "hdrs" in //examples/android/java/bazel:jni_dep. -- MOS_MIGRATED_REVID=106408122
* Quick fix for shipping the android tools in the Bazel binaryGravatar Damien Martin-Guillerez2015-09-03
| | | | | | | | | | | | | | 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
* Require an android_local_tools_repository stanza in the WORKSPACE file so ↵Gravatar Lukacs Berki2015-08-26
| | | | | | | | | | | | | | | 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
* Android example readme: blaze -> bazelGravatar Damien Martin-Guillerez2015-08-26
| | | | | -- MOS_MIGRATED_REVID=101446590
* New-style android exampleGravatar Steven Dee2015-08-04
| | | | | | | | | | | | | - 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
* Update README.md for examples/android to clarify meaning of attribute values.Gravatar John Field2015-07-27
| | | | | -- MOS_MIGRATED_REVID=99179050
* Fixed Android example README.md to make the lists work.Gravatar Alex Humesky2015-07-23
| | | | | -- MOS_MIGRATED_REVID=98856262
* Make --android_crosstool_top default to the android_ndk_repository specified ↵Gravatar Lukacs Berki2015-07-20
| | | | | | | | | | | | | 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
* Add an example Android app and a README.md file that details how to compile it.Gravatar Lukacs Berki2015-07-20
-- MOS_MIGRATED_REVID=98621744
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-17 08:28:14 +0000