What I've seen done elsewhere is to collate all licenses. Last time I checked all components (re)used in mesa had permissive licenses (and this was done by design.) Even if one ends up including a license of a component that's not actually used, one is erring on the safe side.
If one stumbles across any restrictive licenses then one would definitely want to ensure it wasn't actually used (I think this happened in the past, for example, with code used just for build time, or something along those lines.) If one really wanted a precise list of components, the most accurate way would be to use some sort of file-system tracing tool while running meson that listed all files touched when building, but it's probably overkill. Though I'm pretty sure src/glx/ is not used for lavapipe, Jose On Tue, Feb 13, 2024 at 10:08 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 > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
