4 Commits

Author	SHA1	Message	Date
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
MediaPipe Team	296c343332	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. ... This revision builds and runs //mediapipe/util/frame_buffer:all correctly on my mac x86-64 laptop; I haven't yet attempted to build or test on any other platform, so there may well still be glitches, but I think this is more fundamentally sound than what we had before. PiperOrigin-RevId: 515682507	2023-03-10 10:59:17 -08:00
MediaPipe Team	563b193bca	Bump Halide version from 14.0.0 to 15.0.0 and add MacOS Halide dependency ... PiperOrigin-RevId: 515362310	2023-03-09 09:54:19 -08:00
MediaPipe Team	39e2c8351f	Add build system for Halide and expose FrameBufferUtils. ... PiperOrigin-RevId: 515304264	2023-03-09 05:06:18 -08:00