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

	Commit message (Collapse)	Author	Age
*	isable_presubmit	Googler	2018-01-10
\| \| \| \|	PiperOrigin-RevId: 181491528
*	Only copy necessary sources for //src/main/native:embedded_tools.	Xin Gao	2017-11-09
\| \| \| \| \|	Change-Id: I77897c2146d1b1318f966982ef0981c9221f69f7 PiperOrigin-RevId: 175159797
*	Using cc_binary to build windows_jni.dll	Yun Peng	2017-07-31
\| \| \| \| \| \| \|	Get rid of build_windows_jni.sh and the corresponding genrule. Change-Id: I89a199b61109f5687f8b500b60d284cae97f6457 PiperOrigin-RevId: 163679307
*	Windows: check in the icon resource file	Laszlo Csomor	2017-07-27
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The icon resource is a simple object file, built by rc.exe, but rc.exe is part of the Windows Kit, not of Visual Studio, and we have no reliable way to locate it, so we can't reliably rebuild the icon resource from source. Rather than having a brittle genrule that may or may not find the resource compiler, thus may or may not successfully build the icon resource and thus fail the whole build for //src:bazel.exe, let's just use a prebuilt object file. In a subsequent commit I'll add a script that can rebuild this file. Change-Id: Ia1f31ca9e78378088f93c9db144a2b708d690893 PiperOrigin-RevId: 163332738
*	Windows: Bazel now has an icon	Laszlo Csomor	2017-07-27
\| \| \| \| \|	Change-Id: I50a093d4ee1352d7e8958148fec5d577b5eaf00d PiperOrigin-RevId: 163316612
*	Windows, Android BusyBox: create JunctionCreator	Laszlo Csomor	2017-07-10
\| \| \| \| \| \| \| \| \| \| \|	Introduce the JunctionCreator classes that the Android BusyBox can use to work around path length limitations on Windows. See https://github.com/bazelbuild/bazel/issues/3264 Change-Id: Ia5ee39f0635dcc2690ffb1755dc56d21e7bc7536 PiperOrigin-RevId: 161378422
*	build_windows_jni.sh: move file to subdirectory	Laszlo Csomor	2017-07-05
\| \| \| \| \| \| \| \| \| \| \| \| \|	The script more logically belongs in src/main/native/windows than in src/main/native. Also move the //src/main/native:windows_jni rule into //src/main/native/windows:windows_jni, so the logic of building the JNI library is fully contained in that package. Change-Id: I96e19003932cc0ddc5af3471b0b31a1aec09b8fa PiperOrigin-RevId: 160876594
*	Windows, JNI: move around sources	Laszlo Csomor	2017-06-29
	Move the Windows JNI C++ sources to a separate package and separate namespace. This no-op refactoring allows other build rules than Bazel's client library to depend on file I/O and/or JNI functionality. A follow-up commit will split the //src/main/native/windows:processes library into :jni-processes and :jni-file. Change-Id: I33c5f8ebd8961cc440db3b4a95ff78024d7c1d74 PiperOrigin-RevId: 160404298