Can we do Windows builds with clang? #124
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We already ask people to install clang in order to build samples, and the distinction between runtime builds and sample builds is not so clear. Furthermore, MSVC sucks across the board, what with late adoption of C features and terrible command-line setups with vcvarsall and whatnot.
Could we just build the runtime with clang on Windows instead? Then it's one less major dependency to install and probably much less pain and suffering by users.
Unfortunately, throwing clang-cl at it did not work. @MartinFouilleul, this is probably something you'll need to look at since I'm not actually that familiar with everything Orca is using.
One complication is that if we want to use DirectX, MSVC has better support for it than other compilers. It's interfaces are all C++, and thanks to the unstable C++ ABI, other compilers can't use it directly afaik. We could probably try using it with
#define CINTERFACE
, but the DXC shader compiler doesn't support that yet: https://github.com/microsoft/DirectXShaderCompiler/issues/3162.Hm. Maybe I should just get CI working and sidestep the issue then.
Wouldn't we compile shaders offline for the (future) D3D canvas backend?
Yeah that makes sense, I guess we could have a dev-only project whose job it is to build the shaders.
I'm gonna close this since CI will just resolve all this.