Skip to content
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

docs: Add more troubleshooting info for build and run. #4103

Merged
merged 1 commit into from
May 29, 2020

Conversation

agrawal-d
Copy link
Member

Adds command to clean gradle build, and link to upstream
troubleshooting docs.

@agrawal-d agrawal-d requested a review from chrisbobbe May 12, 2020 09:33
@agrawal-d agrawal-d force-pushed the debug-docs branch 5 times, most recently from d219f0c to f1b0ae0 Compare May 14, 2020 11:07
Adds command to clean gradle build, and link to upstream
troubleshooting docs.

[chris: changed `gradlew clean` to `./gradlew clean`]
@chrisbobbe
Copy link
Contributor

Merged, thanks!

I just made one small tweak: changing gradlew clean to ./gradlew clean. My understanding is that sometimes the shell needs a hint that you want it to run a script in a particular file, as opposed to a built-in command or something in the PATH variable — the ./ at the beginning makes it clear that it's a file path. If you didn't cd into android first, you could say android/gradlew, without the leading ./, because it already looks enough like a file path that it's reasonable to assume it is one.

@chrisbobbe
Copy link
Contributor

And without the leading ./, I get this:

$ gradlew clean
bash: gradlew: command not found

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants