MediaPipe Team
1aa5e0d46f
No public description
...
PiperOrigin-RevId: 560689326
2023-08-28 06:21:09 -07:00
MediaPipe Team
ff17846c6a
No public description
...
PiperOrigin-RevId: 557490568
2023-08-16 08:16:30 -07:00
MediaPipe Team
e37bedd344
Fix Halide BUILD rules
...
PiperOrigin-RevId: 547755467
2023-07-13 04:47:34 -07:00
Sebastian Schmidt
e84799ee37
Internal change
...
PiperOrigin-RevId: 521483663
2023-04-03 09:45:42 -07:00
MediaPipe Team
a4923ca7aa
Internal compatible_with change
...
PiperOrigin-RevId: 520751319
2023-03-30 15:01:09 -07:00
Jiuqiang Tang
984073bf73
Fix the "'<>' with anonymous inner classes is not supported" error.
...
PiperOrigin-RevId: 520705926
2023-03-30 12:05:08 -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
39e2c8351f
Add build system for Halide and expose FrameBufferUtils.
...
PiperOrigin-RevId: 515304264
2023-03-09 05:06:18 -08:00
