bazel - a fast, scalable, multi-language and extensible build system

	Commit message (Collapse)	Author	Age
*	Move the default cquery output format to its own callback and standardize ↵	juliexxia	2018-03-27
\| \| \| \| \| \|	cquery output callback logic PiperOrigin-RevId: 190667120
*	Create a new output formatter for cquery which output transition information ↵	juliexxia	2018-03-23
\| \| \| \| \| \|	in either a FULL or LITE version. Trigger new output with the new --transitions cquery flag in the new CqueryOptions class. PiperOrigin-RevId: 190278664
*	Create a new version of BuildTool that holds all cquery logic.	juliexxia	2018-03-07
\| \| \| \|	PiperOrigin-RevId: 188212286
*	Implement the config(expr, word) cquery function.	juliexxia	2018-02-13
\| \| \| \| \| \| \|	expr - the expression to be evaluated word - the configuration (represented by the strings 'host', 'target', or 'null') to try to find the result(s) of 'expr' in. If some but not all results of expr can be found in the specified config, then the subset that can be is returned. If no results of expr can be found in the specified config, then an error is thrown. PiperOrigin-RevId: 185572590
*	PiperOrigin-RevId: 185383460	juliexxia	2018-02-12
\|
*	Add a "direct" mode to "blaze run" that makes the process being run a direct	lberki	2018-02-05
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	child of the process where the Blaze client itself was run. Limitations: - Untested on Windows; it should work because ExecuteProgram() is implemented there, too, but since Windows doesn't support exec(), there is at least one process in between Progress towards #2815. RELNOTES[NEW]: The new "--direct_run" flag on "blaze run" lets one run interactive binaries. PiperOrigin-RevId: 184528845
*	Move storage of queryExpression for cquery out of BuildRequest and straight ↵	juliexxia	2018-01-19
\| \| \| \| \| \|	into processRequest method in BuildTool. This is an extension of CL/181816980 and prevents pollution of BuildRequest. PiperOrigin-RevId: 182576704
*	Introduce the blaze cquery command as the new ui for configurable query.	juliexxia	2018-01-12
	before: blaze build --nobuild //foo --experimental_post_build_query="deps(//foo)" after: blaze cquery "deps(//foo)" pros of ui change: - more concise - assumes query expression targets == targets to be built (but allows for flexibility through --top_level_targets flag) - separate from build command - cquery command recognizes query options, build options, and its own unique set of options cons of ui change: - adds another command to blaze - recognizes options that don't actually work yet -> requires more option validation RELNOTES: None PiperOrigin-RevId: 181816980