gradlew projects -The new moved projects are unsurprisingly named like their former "make" -counterparts. To find the list of project-names you can use with gradle: - $. gradlew lint:check => runs tests and checks such as findbugs. gradlew lint:assemble => builds but do not run tests. gradlew lint:tasks - Generally there are only 2 task names to remember: - $. To get a list of possible tasks, try this: $. Gradle targets are in the form "project-name:task-name". If you want to know more, visit - On Windows with the CMD shell, use. gradlew lint:build -Output is located in $TOP/out/host/gradle/tools/base/lint/libs/ -Some comments/tips: - Gradle is a build system, a bit like make or ant. To build it from the command-line, you'd use "gradle" as such: -$ cd tools/base -$. 1- I don't build full SDKs but I want to change tool X: -Let's say as an example you want to change lint. These prebuilts are the -ones being used when doing a "make sdk". If you need to view/change the source and lack these folders, you can bring -them by using a repo init command such as: -$ repo init -u -g all,-notdefault,tools -$ repo sync -The libraries that are sourced in tools/base and tools/swt are converted to -prebuilts which are located in prebuilts/devtools. Instead they can be found in the tools/base.git and the tools/swt.git projects. +++ -1,112 +0,0 of the SDK tools sources have moved out of the sdk.git project. Some parts are still needed, so leaving those.Ĭhange-Id: I47e8af146c4855aaf642fd3b9b10d3cd60a401d6 diff -git a/README.txt b/README.txt
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |