aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/docs/bazel-and-android.md
Commit message (Collapse)AuthorAge
* Add Bazel + Android codelab to Android Resources pageGravatar Jingwen Chen2018-07-23
| | | | | | Closes #5598. PiperOrigin-RevId: 205662280
* Documentation for Android NDK support with BazelGravatar jingwen2018-07-11
| | | | | | | Example workspace: https://github.com/bazelbuild/examples/pull/66/files RELNOTES: None. PiperOrigin-RevId: 204162234
* Update "Android and Bazel" page with more descriptive texts, and also added ↵Gravatar jingwen2018-04-12
| | | | | | | a point about Android Instrumentation Tests. RELNOTES: None. PiperOrigin-RevId: 192707296
* Remove the table of contents from the Android and Bazel page. I clicked on ↵Gravatar jingwen2018-03-14
| | | | | | | the link, expecting to be redirected to a new page, but it's just an anchor link on the same page. The page is short enough to not need a ToC. RELNOTES: None. PiperOrigin-RevId: 189042068
* Added asteinb's Android Builds blogpost to the Android and Bazel pageGravatar Jingwen Chen2018-03-09
| | | | | | Closes #4693. PiperOrigin-RevId: 188488139
* Remove the word 'Skylark' when it doesn't add any value.Gravatar laurentlb2017-12-14
| | | | | | | | | | | The word Skylark tends to be overused. We should use it only when we refer to the language itself. In many places, the word 'Skylark' was used, even if the reader may not know it (e.g. "create a rule" is clearer than "create a Skylark rule"). RELNOTES: None. PiperOrigin-RevId: 179024448
* Create the "Android and Bazel" and "Apple apps and Bazel" pages.Gravatar Googler2017-09-14
PiperOrigin-RevId: 168577347