4 ms·
The license (and the code) for dxil.dll/libdxil.so isn't in that repo, they just include the blob in releases. If you look at a release you'll see an additional
by zerocrates 3y ago
The license (and the code) for dxil.dll/libdxil.so isn't in that repo, they just include the blob in releases. If you look at a release you'll see an additional LICENSE-MS.txt that just covers that dxil signing library.
- yazzku 3y agoHow is that compatible with the GPL licence from autoconf?
- Dylan16807 3y agoYou mean the config.guess script? That's a completely different program. GPL doesn't jump across programs.
- zerocrates 3y agoLooks like the only autoconf bit they use is an old copy of config.guess that was used in the LLVM they forked from (I think they've since taken it out entirely in the LLVM upstream). There's actually a carveout in config.guess's license that lets you redistribute it under whatever license you want but only if you're actually using an autoconf-based build. The LLVM version this is based off of only uses config.guess and not anything else from autoconf, so that carveout doesn't apply. Instead LLVM just relied on the fact that config.guess is only getting called via the command line, so the GPL's "virality" doesn't apply; LLVM (and now Microsoft) just distributed config.guess separately licensed as GPL alongside their code.
- p_l 3y agoGPL doesn't care about inclusion or linking, it cares about derivative work. And somehow I doubt the 3d engine is derivative work of a piece of autoconf.
- nextaccountic 3y agoOn the latest release https://github.com/microsoft/DirectXShaderCompiler/releases/tag/v1.7.2308 https://github.com/microsoft/DirectXShaderCompiler/releases/... There are "source code" files in zip and tar.gz Aren't those source code for those dlls?
- nhubbard 3y agoNo, that’s a GitHub thing — it just downloads the Git repo at that release tag, which doesn’t include the source code in this case