jgehw 5945950b25 [tensorflow-cc] fix build issues on Windows (#12546) ... * fix build issues occurring from default bazel config being used because customized bazel config is stored in wrong directory * [tensorflow-cc] Update CONTROL and ci.baseline.txt * fix also applies to windows static build * Revert "fix also applies to windows static build" * leave variables unset in order to let bazel auto-detect them the same way it auto-detects include path avoiding mismatches between toolset and include files versions * bazel VC auto-detect doesn't work (it ends up in a dev command prompt and tries to parse it), so fix the issue of inconsistency of toolset versions between auto-detection in vcpkg and bazel by letting vcpkg determine everything including toolset version * see if updating really outdated bazel fixes finding correct VC tools on Azure DevOps * setting x64-windows CI to fail again It doesn't work if more than one VC toolkit is installed. Likely a bug in bazel. bazel is currently v3.4.1, however tensorflow v1.14 requires really outdated bazel v0.25. Going to upgrade tensorflow to v2.3 and then using up-to-date bazel, but will do this in a separate pull request, as it requires more work. * revert bazel upgrade as tensorflow v1.14 requires outdated bazel 0.25 Co-authored-by: Gehweiler <Joachim_Gehweiler@McAfee.com> Co-authored-by: wangli28 <wangli28@beyondsoft.com>		2020-08-07 12:08:51 -07:00
..
CONTROL	[tensorflow-cc] fix build issues on Windows (#12546)	2020-08-07 12:08:51 -07:00
file-exists.patch
fix-build-error.patch
portfile.cmake	[tensorflow-cc] fix build issues on Windows (#12546)	2020-08-07 12:08:51 -07:00
TensorflowCCConfig.cmake