Dan Willemsen 87b17d1ff4 Use SRCDIR as a working directory ... 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		2015-09-17 23:42:25 -07:00
..
arm64_device.go	Use SRCDIR as a working directory	2015-09-17 23:42:25 -07:00
arm_device.go	Use SRCDIR as a working directory	2015-09-17 23:42:25 -07:00
builder.go	Use SRCDIR as a working directory	2015-09-17 23:42:25 -07:00
cc.go	Use SRCDIR as a working directory	2015-09-17 23:42:25 -07:00
cc_test.go	Add support for building on Darwin hosts	2015-05-07 14:09:48 -07:00
clang.go	Update flags to match make	2015-09-15 22:20:03 +00:00
gen.go	Fix java resource glob file list location	2015-08-24 16:19:43 -07:00
toolchain.go	Add support for building NDK modules.	2015-03-26 21:58:12 -07:00
util.go	Add support for include_files	2015-09-14 16:09:36 -07:00
x86_darwin_host.go	Update flags to match make	2015-09-15 22:20:03 +00:00
x86_linux_host.go	Update flags to match make	2015-09-15 22:20:03 +00:00