All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: understanding recipes
Date: Fri, 27 Jan 2012 10:43:12 -0800	[thread overview]
Message-ID: <4F22F040.3000109@linux.intel.com> (raw)
In-Reply-To: <4F21CF79.5060909@intel.com>

On 26/01/12 14:11, Scott Garman wrote:
> In this case, the LIC_FILES_CHKSUM is storing the md5sum of the COPYING
> file, which is stored in the top-level directory of the extracted sources.
>
> So manually download the hello version you are trying to use, extract
> the tarball locally, and run md5sum against the COPYING file. Then
> update the LIC_FILES_CHKSUM field with that new md5 checksum.

Or if you're lazy, like me, you can just run the build and let it fail 
then run md5sum on the extracted source in the work directory.

i.e. for qemux86 hello world I could bitbake helloworld then:

md5sum tmp/work/i586-poky-linux/hello-world-2.7-r0/hello-world-2.7/COPYING

Cheers,
Joshua
-- 
Joshua Lock
         Yocto Project "Johannes factotum"
         Intel Open Source Technology Centre


  parent reply	other threads:[~2012-01-27 18:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 16:44 understanding recipes jfabernathy
2012-01-26 16:48 ` Jack Mitchell
2012-01-26 18:55 ` Scott Garman
2012-01-26 21:29   ` jfabernathy
2012-01-26 21:32   ` jfabernathy
2012-01-26 21:38     ` Scott Garman
2012-01-26 21:42       ` jfabernathy
2012-01-26 22:04       ` jfabernathy
2012-01-26 22:11         ` Scott Garman
2012-01-26 22:36           ` jfabernathy
2012-01-26 22:37           ` Gary Thomas
2012-01-26 23:44             ` jfabernathy
2012-01-26 23:52               ` Gary Thomas
2012-01-27  1:12                 ` jfabernathy
2012-01-27  1:20                   ` Saul Wold
2012-01-27  3:14                 ` Scott Garman
2012-01-27 18:43           ` Joshua Lock [this message]
2012-01-28  1:42             ` McClintock Matthew-B29882
2012-01-28 10:13               ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F22F040.3000109@linux.intel.com \
    --to=josh@linux.intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.