You should only see the MIT license for all Mesa contributions that don't import external source code.
Marek On Tue, Feb 13, 2024 at 5:23 AM George Karpathios <gkar...@gmail.com> wrote: > > Hi everyone, > > I'd like to bundle Lavapipe's binary that I've built (also contains LLVM > thanks to static linking) with a commercial application and I'm confused > regarding which licenses I should include into the product. Reading in > https://docs.mesa3d.org/license.html, "Different copyrights and licenses > apply to different components" and "In general, consult the source files for > license terms." makes me think that I should search into every component that > Lavapipe uses (how can I figure these out precisely?), is that correct? For > example, do I need the licenses for LLVM, Main Mesa code, Gallium, llvmpipe > and more? Additionally, looking inside Lavapipe's source files under > src/gallium/frontends/lavapipe, I see various license texts from RedHat, > Intel, AMD, Valve, VMware etc. > > I feel a bit overwhelmed as to what's the proper thing to do, so if anyone > could help me learn how to figure situations like this out, I would be really > grateful. Thanks in advance. > > Best regards, > George
