-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add documentation for Android Studio with Bazel on all OS's [Blocks: #2745] #2746
Comments
Regarding this, I've followed these steps.
But on selecting the bazel on the option disappears.
For this after installing the BAZEL plugin
But there are a bunch of error in the bazel console (bazel sync fails and I guess we can't proceed after this) @BenHenning @fsharpasharp Do we have to wait for a new release for this or make changes in the plugin or Am I using a wrong approach here. Making |
To fix this I've replaced the installed bazel with oppia-bazel and then when I try to sync the project I get this error Created a gist of the targets which gives the error (errors encountered while analyzing target)
|
There's a new issue affecting Android Studio: bazelbuild/rules_proto#78 (see linked protoc issue for details). I might try sending a patch to rules_proto to see if it's an easy fix just to bump the version to 3.14. |
Confirming this is an issue with version 2021.01.06.0.1 of the Bazel plugin. Updating rules_proto to a later version doesn't seem to fix the issue. I think the issue is actually within the Bazel plugin--it's not being built with compatibility for JDK 8. In the meantime I'm going to see if downgrading to an earlier version of the plugin fixes the issue. |
bazelbuild/intellij#2265 is tracking the plugin-specific issue. |
Confirming that the custom plugin suggested in that thread does work for us: https://github.com/hedronvision/bazelbuild-intellij/releases/tag/v2021.02.03. @fsharpasharp FYI since this is definitely going to cause some friction when trying to get Bazel working in Android Studio. |
I've tried using the latest version of bazel plugin (2021.04.27.0.0) for the to build using bazel. I've created a gist for the errors I've encountered. |
Ah, that might be a different error @FareesHussain. Could you add your .bazelproject file to a Gist & link that here? Also, which Android SDK do you have installed on your system? |
Here is the gist the plugin showed SDK 29 and 30 as available and I selected 30 |
I was trying to install from disk by downloading the build but it gives the above error |
…ions for different Operating System (#4926) <!-- READ ME FIRST: Please fill in the explanation section below and check off every point from the Essential Checklist! --> ## Explanation Fix Part of #2746 : Added Bazel Installations instructions for different Operating System <!-- - Explain what your PR does. If this PR fixes an existing bug, please include - "Fixes #bugnum:" in the explanation so that GitHub can auto-close the issue - when this PR is merged. --> ## Essential Checklist <!-- Please tick the relevant boxes by putting an "x" in them. --> - [x] The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".) - [x] Any changes to [scripts/assets](https://github.com/oppia/oppia-android/tree/develop/scripts/assets) files have their rationale included in the PR explanation. - [x] The PR follows the [style guide](https://github.com/oppia/oppia-android/wiki/Coding-style-guide). - [x] The PR does not contain any unnecessary code changes from Android Studio ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#undo-unnecessary-changes)). - [x] The PR is made from a branch that's **not** called "develop" and is up-to-date with "develop". - [x] The PR is **assigned** to the appropriate reviewers ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section)).
We should expand our Bazel documentation to include:
Also, per #3371 Bazel development support is very limited on Windows. Per #3437 we should investigate the viability of setting up a VM and running both Android Studio and Bazel from the same Unix-based environment (to avoid a bifurcation where the repo lives in Windows and the user does development via Windows Android Studio, but uses Bazel within an Ubuntu subsystem). This involves documenting the steps below for Windows:
The text was updated successfully, but these errors were encountered: