Hi Vivek, Il 20 ott 2016 1:42 PM, "Vivek Per" <pervi...@gmail.com> ha scritto: > > Hi All, > > Thank you very much this recipe worked for me.
If it worked, as already suggested by Ross, please consider posting it to the mailing list for further review and hopefully for merging into meta-oe or where it belongs best. Instructions for contributing can be found at https://github.com/openembedded/meta-openembedded/blob/master/README and in READMEs from each layer. > > Thanks and Regards, > > > On Thu, Oct 20, 2016 at 3:40 AM, Burton, Ross <ross.bur...@intel.com> wrote: >> >> Please considering posting these recipe into meta-oe or similar, tomcrypt etc comes up every few months. And posting a recipe to the list implies you want review, right? :) >> >> On 19 October 2016 at 10:12, Markus Volk <f_...@t-online.de> wrote: >>> >>> DESCRIPTION = "tomcrypt" >>> HOMEPAGE = " http://www.libtom.net"; >>> LICENSE = "DWTFYW" >> >> Second worst license known to man. :( >>> >>> LIC_FILES_CHKSUM = "file://${S}/LICENSE;md5=71baacc459522324ef3e2b9e052e8180" >> >> These URLs are relative to ${S} so just file://LICENSE works. >>> >>> SRC_URI = "git://github.com/libtom/libtomcrypt.git;branch=develop \ >>> " >>> >>> SRCREV = "${AUTOREV}" >> >> In general it's recommended to use a fixed SHA and then override SRVREV if you need to for testing/CI/whatever. >>> >>> PV = "${SRCPV}" >>> PR = "1" >> >> No need for PR in general. >>> >>> S = "${WORKDIR}/git" >>> >>> inherit autotools-brokensep >> >> Boo. Is upstream fixable or is it beyond help? >>> >>> SRC_URI[md5sum] = "d2f152e4dc83ee4cdb1b4f1a4866fe7f" >>> SRC_URI[sha256sum] = "d0ff89397f9a5fd1d13b1cbc419d5d426e14473135515d72bfcb58e5babf5032" >> >> No need for SRC_URI if you're using git fetcher. >> >> Ross > > > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
