Thanks all for your quick response. You have given me something to think of so I will look into it to see if some of my issues are related to the way we have set things up. I will post my findings once I have gone through your comments to see if we could use it in our build.
Thanks Den ons 6 apr. 2022 kl 11:23 skrev <[email protected]>: > > Hi > > I set INCOMPATIBLE_LICENSE_append = " GPLv3 GPLv3+ LGPLv3 LGPLv3+" > but then allow compiling several recipes with those licenses as long > as they don't end up on images and in the product. For example: > > ... > WHITELIST_GPL-3.0+ += "cairo" > PACKAGE_EXCLUDE += "cairo-src cairo-dbg cairo-perf-utils cairo-staticdev > cairo-locale" > > WHITELIST_GPL-3.0 += "binutils" > PACKAGE_EXCLUDE += "binutils-dbg binutils-staticdev binutils-dev binutils-doc > binutils-locale libbfd binutils" > > WHITELIST_GPL-3.0 += "gdb" > PACKAGE_EXCLUDE += "gdb-sdktests-dbg gdb-sdktests gdbserver gdb-dbg > gdb-staticdev gdb-dev gdb-doc gdb-locale gdb" > ... > > I do this in the distro config. > > Results works but you may need to revisit several recipes and detect where > exactly > the GPLv3 license is being used. > > bash dependency is annoying but products can be made without. Same for GNU > readline > support. > > These are much work and better then using meta-gplv2 with its unmaintained SW > versions. > > Would be nice to collaborate in yocto upstream on a build config which > disables most > GPLv3 packages from rootfs but keeps the development tools etc working in > the SDK. > > Cheers, > > -Mikko
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56676): https://lists.yoctoproject.org/g/yocto/message/56676 Mute This Topic: https://lists.yoctoproject.org/mt/90285507/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
