Dan Albert

@lzhido: how did you build your app? It looks like you linked the validation layer libraries directly. I think that's the problem. Vulkan loads those at runtime as long as...

Glad I could help. You may want to subscribe on https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/8167, which would let you do this even more simply.

This isn't a bazel issue, nor even a bug. Static initialization order is not defined. You need explicit initialization if you care about order. That's not our choice, that's how...

Reading through to the LLVM bug you linked, I guess LLVM has some sort of attribute to hack around that? idk how that's implemented so it may not be portable....

We don't document when clang internals move around, no (we aren't usually aware that it's happened). The libandroid_support removal is a part of the kitkat removal. It was never needed...

That's how ndk-build deals with it. If it's an option for you it's going to be the most future proof path.

> But I believe the new NDK only provides dmg files, not zip files The zip file still exists, it's just not published on the download pages because people kept...

I see it's already the case here... but why would NDK builds use a different default standard version than other platforms? That seems prone to confusing users. As a user...

I don't know if there is another bazel standard (I'm not a bazel user, I just lurk here because I work on the NDK). If bazel doesn't aim to be...

IMO, better to go a step further and migrate people to https://github.com/google/cpu_features. The only reason the NDK still ships its own is because we don't want to break existing builds...