MediaPipe Team 733216da7e Use "x86_32" instead of "i386" for Bazel CPU ID -- they are currently synonyms, but "i386" is likely to be deprecated and removed in the future. ... PiperOrigin-RevId: 520865783		2023-03-31 02:06:53 -07:00
..
BUILD	Add build system for Halide and expose FrameBufferUtils.	2023-03-09 05:06:18 -08:00
BUILD.bazel	Revise the Halide Bazel build rules to be cleaner and more correct. The initial version we landed happened to work (at least in most cases) but had known workarounds in it. AFAICT, the issue seemed to be that the MediaPipe config_setting() values we were using didn't always resolve to the right thing when detecting the host cpu (vs the compile-target cpu), which is critical for Halide. I fixed this by avoiding the use of the MediaPipe config_settings entirely, using instead the public Bazel settings hosted at https://github.com/bazelbuild/platforms.	2023-03-10 10:59:17 -08:00
halide.bzl	Use "x86_32" instead of "i386" for Bazel CPU ID -- they are currently synonyms, but "i386" is likely to be deprecated and removed in the future.	2023-03-31 02:06:53 -07:00