minimal image without GPLv3
Hi,
I am yocto-izing people again and someone asked how to build a minimal Yocto image without GPLv3 components.
I said like this[1]
1. Comment out the EXTRA_IMAGE_FEATURES line
2. Set INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3.0"
... and indeed a core-image-minimal was built with alternative packages like busybox instead of bash ...
but it did not run on qemu due to some kernel issues.
I did not investigate it further, but is this s known problem?
Regards,
Robert
[1]
http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#ref-images...Programming
today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
Hi Robert,
Quoted 8 lines · On Tue, 26 Jul 2016 09:21:34 Robert Berger wrote:
I am yocto-izing people again and someone asked how to build a minimal Yocto image without GPLv3 components.
I said like this[1]
1. Comment out the
EXTRA_IMAGE_FEATURESline
2. SetINCOMPATIBLE_LICENSE= "GPL-3.0 LGPL-3.0 AGPL-3.0"
Quoted 6 lines
... and indeed a core-image-minimal was built with alternative packages like busybox instead of bash ...
but it did not run on qemu due to some kernel issues.
I did not investigate it further, but is this s known problem?
Not that I know of - and on the face of it it seems unlikely that this would be related, unless perhaps the bootloader changed - most of the parts that are switched out under these circumstances are part of userspace; the tools used to build the kernel should be the same.
In any event this sort of thing shouldn't happen. Could you perhaps file a bug for this with more details?
Thanks,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre