SCons will automatically use tapi in dynamic link builds on macos. Tapi generates a file which represents the API of some shared library. This allows one to not relink or rebuild things which use the API, and still allow changes to the implementation under that API.

Bazel is not configured to use or produce tapi files (.tbd) so SCons is asking bazel to build them, and bazel does not, resulting in build failure. 

We should decide if bazel should support tapi (if not we can force TAPI= in the scons env), and then configure the integration to act appropriately.

We should also consider adding some basic level of macos dynamic link coverage to CI as some developers use this configuration.