build_soong - Fork of build/soong

	Commit message (Collapse)	Author	Age	Files	Lines
*	Simplify bootstrapping	Dan Willemsen	2016-08-31	1	-4/+1
\| \| \| \| \| \|	Follow changes from https://github.com/google/blueprint/pull/121 Change-Id: Icc5003f6e8592a667e1ce5e58361c03997078763
*	Update path to ninja	Colin Cross	2016-05-04	1	-1/+1
\| \| \| \| \| \| \|	ninja has been moved from prebuilts/ninja to prebuilts/build-tools so it can share the hermetic libc++.so there. Change-Id: I0b6e76baaa6916a8c7fd19c684b792ccef2f9cb1
*	Turn on ninja errors for duplicate rules	Dan Willemsen	2016-03-01	1	-1/+1
\| \| \| \|	Change-Id: Iadac88f8835121a8685bff835acba638100bb654
*	Execute the blueprint wrapper	Dan Willemsen	2015-12-10	1	-3/+2
\| \| \| \| \| \| \| \|	See https://github.com/google/blueprint/pull/86 for the blueprint change and description. Bug: 25448631 Change-Id: Ibadbfc8e2cf2592dcfd137156fc3681819078328
*	Use SRCDIR as a working directory	Dan Willemsen	2015-09-17	1	-12/+9
\| \| \| \| \| \| \| \| \| \| \|	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
*	Fix soong scripts to support directories with spaces	Colin Cross	2015-04-10	1	-13/+13
\| \| \| \| \| \| \| \| \| \| \|	Using a path with a space to execute soong is unlikely, but it might as well work. Quote all the paths in the soong scripts. Soong and blueprint will still both fail if the relative path between the soong script and the source directory has a space in it, but this is even more unlikely. Change-Id: I8986f10115209d69b09b82ffea26e4b10d29c197
*	Fix running soong from different directory	Colin Cross	2015-04-09	1	-2/+2
\| \| \| \| \| \|	${BOOTSTRAP} already contains ${BUILDDIR} Change-Id: Ie1303e4b2a5ce415f565ffc4b6125071e427bd43
*	Support dependencies on environment variables	Colin Cross	2015-03-26	1	-0/+17
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Ninja can't depend on environment variables, so modifying build behavior based on environment variables requires coordinating between the soong script that invokes ninja and the soong_build manifest generator. Allow any module to call Config.Getenv to get the contents of an environment variable while registering a dependency on it. After all modules have been processed write out the state of all used environment variables to a JSON file called .soong.environment. During the next build the soong script will use the soong_env tool to compare the contents of .soong.environment to the current environment, and force a build manifest regeneration by deleting the .soong.environment file if any variables have changed. Change-Id: Id0d81933a857bc2fc1cd7a393a3c6cec73dc4824
*	Replace soong script with a symlink	Colin Cross	2015-03-25	1	-0/+30
	bootstrap.bash creates a soong script in the output directory using build/soong/soong.in. This requires a manual rebootstrap any time soong.in changes. Instead, have bootstrap.bash symlink build/soong/soong.bash to soong in the output directory, and create a file called .soong.bootstrap in the output directory that contains the variables that bootstrap.bash sets. Change-Id: I5e6e54c2e8bdde876941e2e082f9ba177c757cbf