Alex Reinking

> Also, perhaps unrelated, `abseil-cpp` doesn't compile due to [...] I wasn't aware any of our apps depend on Abseil! I wouldn't worry about it, since it's just an app....

This does seem worth evaluating now that the buffer protocol is back.

> Halide is designed to be extensible (e.g. Func::add_custom_lowering_pass). People extending Halide may want to reuse all sorts internal tools from outside the compiler. It's also nice to be able...

> Not sure what flags we tried, you may want to experiment. For llvm we already dead-strip all symbols not used by Halide itself in the makefile build via linker...

I've started running into issues on Windows with CMake 3.19 regarding exported symbols not being found. This might have to do with `WINDOWS_EXPORT_ALL_SYMBOLS` flakiness; remember: this is a CMake/Kitware-maintained convenience...

> I guess if anything in Halide.h uses LLVM types, that might not work well. I'm pretty sure we require that this doesn't happen. So if it does, somehow, it's...

I think I need to learn a bit more about Windows development, here. The last time we tried this on MSVC, we ran into issues with the way Windows is...

On Python 3.8 there's a new `add_dll_directory()` API that might be able to help us work around this. See: https://docs.python.org/3/whatsnew/3.8.html#ctypes See: https://docs.python.org/3/whatsnew/3.8.html#bpo-36085-whatsnew See: https://docs.python.org/3/library/os.html#os.add_dll_directory See: https://bugs.python.org/issue36085 See: https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order

> Is this windows-only? I believe so, yes. RPATH saves us on other systems.

I have moved the sanitizer environment variables to presets for a few reasons: 1. They were complicating our build rules considerably and necessitated hacks in custom commands. 2. As environment...