Hi Christian, On 12/10/2014 10:51 PM, Christian Ege wrote: > Hello Mathias, > Am 10.12.2014 20:25 schrieb "Matthias Fuchs" <[email protected]>: >> >> Hi, >> >> what's the best way to collect all sourcecode and licenses that are >> involved in an ELDK/yocto based target image? So that these files can be >> used to provide the complete sourcecode for a given target (in order to >> fulfill license demands) >> >> One method could be to provide the ELDK git repository and the download >> directory that is created during the build process. But this contains >> more sources than are required to build a special target image (also >> contains toolchain and other images releated files). >> >> The installed_pkgs.txt file only lists the package names and not the >> sources itself. >> >> I expect this to be a common task when creating yocto based products. >> But I did not find the best way so far. >> > Yes, you can do it. The yocto project has some documentation on this. > http://www.yoctoproject.org/docs/1.6.1/dev-manual/dev-manual.html#maintaining-open-source-license-compliance-during-your-products-lifecycle > > Due too the fact that eldk is based on yocto this should apply to eldk as > well. > > We create for example a DVD image with all related source + Licence > information for every release build. Thanks for pointing up. That will help.
Matthias _______________________________________________ eldk mailing list [email protected] http://lists.denx.de/mailman/listinfo/eldk
