No description
The existing behavior of using the build directory as the working directory is useful if you want to move/copy the output directory around and SRCDIR still refers the the source. But, it's more useful to have the source directory be the working directory. Tools like cpp(__FILE__) and other debug prints embed relative paths from the working directory. We also have tools that expect the working directory to be $TOP. Change-Id: Ia0f1d3c6b7df72d61cf5628efa2baa98bd19775b |
||
|---|---|---|
| androidbp/cmd | ||
| androidmk | ||
| cc | ||
| cmd | ||
| common | ||
| env | ||
| genrule | ||
| glob | ||
| java | ||
| Android.bp | ||
| bootstrap.bash | ||
| build.ninja.in | ||
| copygcclib.sh | ||
| doc.go | ||
| register.go | ||
| root.bp | ||
| soong.bash | ||
| soong.bootstrap.in | ||