Fix list of cxx_builtin_include_directories. Only a few are needed, but those are more complicated (mix of symlinked and real paths).
Properly return error from crosstool wrapper.
PiperOrigin-RevId: 318788040
Change-Id: Ia66898e98a9a4d8fb479c7e75317f4114f6081e5
I think the preconfig hasn't been updated since cl/308598480. Most users have moved off of preconfigs, but some remain.
Manually, because the update.sh script is broken for me.
PiperOrigin-RevId: 314310108
Change-Id: I746ac0ac62f90bef6624eedf01c7be7a346a2dfd
This is needed for tf.distribute multi worker tests. Those tests use multi processes to simulate multiple workers, and need to serialize test arguments and results. pickle is too limited.
PiperOrigin-RevId: 313463711
Change-Id: Id01c997bf1b2f2cc98b90357759ecf1c2c0bd7c4
Added new script build_pip_package_with_bazel.sh.
This scirpt can be used with ci_build.sh of TF for cross building.
ex) Build armhf Python3 based PIP
$ CI_DOCKER_EXTRA_PARAMS="-e CI_BUILD_PYTHON=python3 -e CROSSTOOL_PYTHON_INCLUDE_PATH=/usr/include/python3.5" \
tensorflow/tools/ci_build/ci_build.sh PI-PYTHON3 \
tensorflow/lite/tools/pip_package/build_pip_package_with_bazel.sh armhf
PiperOrigin-RevId: 312420603
Change-Id: I5504fb22248e6a9d29560fa9216113a8705b7399
Instead of using --config=rbe_linux_cuda_clang --config=rbe_linux_py3, users
can now use --config=rbe_linux_cuda_clang_py36 (or any other supported version)
to build on RBE with the respective python version.
PiperOrigin-RevId: 309043827
Change-Id: Id0299a6ceca8e050eec63907f317c7a2c3058031
Update missing toolchain systempath to include python files correctly.
This regression happens by PR #38399.
Also skip OpenBLAS build for RPI 2/3 to improve build speed.
PiperOrigin-RevId: 308721738
Change-Id: I42a1ff1b104190ba3de7644f1af8d12997b7dd1e
Add two repository rules:
- @local_execution_config_platform: local platform to allow selecting locally
executed tools on
- @local_execution_config_python: python configured for execution...
PiperOrigin-RevId: 307862682
Change-Id: Ie0320f2f137a40b418632989981c9dc072ef80e6
- @local_execution_config_platform: local platform to allow selecting locally
executed tools on
- @local_execution_config_python: python configured for execution on the local
machine during otherwise remote builds
Mark rules that are required to run locally to require our local platform.
This allows pyth...
PiperOrigin-RevId: 307771596
Change-Id: If1f0013ec88a35d507b2b622894208aab2416fe5
- @local_execution_config_platform: local platform to allow selecting locally
executed tools on
- @local_execution_config_python: python configured for execution on the local
machine during otherwise remote builds
Mark rules that are required to run locally to require our local platform.
This allows python paths to differ between the remote docker image and local
machine.
For example, the local machine might have python 3.7 installed in
/usr/bin/python3, while the remote docker should use a python installed
in /usr/local/bin/python3.8.
PiperOrigin-RevId: 307585019
Change-Id: I29313121beb967b77ae123e7d1b614c688cb40ca
- @local_execution_config_platform: local platform to allow selecting locally
executed tools on
- @local_execution_config_python: python configured for execution on the local
machine during otherwise remote builds
Mark rules that are required to run locally to require our local platform.
This allows python paths to differ between the remote docker image and local
machine.
For example, the local machine might have python 3.7 installed in
/usr/bin/python3, while the remote docker should use a python installed
in /usr/local/bin/python3.8.
PiperOrigin-RevId: 307558811
Change-Id: I0dc2d877a7c26b294bf2b569b4f121cf6506e7fc
