All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jim Rafert <jimr@spectralogic.com>
Cc: yocto@yoctoproject.org
Subject: Re: How do I create a recipe for laying down post-build config files?
Date: Tue, 10 Jun 2014 09:53:46 +0100	[thread overview]
Message-ID: <2167937.Ioj4ylAJNq@peggleto-mobl5.ger.corp.intel.com> (raw)
In-Reply-To: <86196249137E0843B2E0673D4F731E0CAB521799@reactor.sldomain.com>

Hi Jim,

On Monday 09 June 2014 21:44:00 Jim Rafert wrote:
> I'm trying to gather all my post-build tweaks into a recipe that will be
> built as part of an upper-level layer, so that they are installed after the
> meta layer is processed.  Many of these could be accomplished as part of
> .bbappend files for the recipes that originally supply the config files,
> but I wanted to gather all my customizations in one spot, so that they're
> easy to find.
> 
> The recipe doesn't actually build anything, so there's no do_build task.
> 
> This is surely something that is commonly wanted.
> 
> Here's my current recipe, in spectra-postbuild_0.1.bb.
> 
> When I try to build an image, the build fails with
> ERROR: QA Issue: spectra-postbuild: Files/directories were installed but not
> shipped /RELEASE-NOTES.txt
> 
> When I disable the installed-vs-shipped QA test,  it fails later when it
> can't find a package file.

In general, disabling installed-vs-shipped is not the right thing to do. What 
it's trying to tell you is that you've installed a file in do_install and then 
haven't packaged it in any package, which means it can never end up in the 
final image.

FYI we've been putting together a section for the manual in the upcoming 1.7 
release that attempts to explain each warning and what to do to resolve it; 
here is a preview:

http://www.yoctoproject.org/docs/1.7/ref-manual/ref-manual.html#ref-qa-checks

If "fails later when it can't find a package file" means during do_rootfs, this 
is almost certainly because the package ended up empty and thus wasn't created 
(we don't create empty packages unless ALLOW_EMPTY for the package is set to 
"1", but generally the fix is to ensure the files you expect to be packaged into 
the package are actually packaged).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  parent reply	other threads:[~2014-06-10  8:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 21:44 How do I create a recipe for laying down post-build config files? Jim Rafert
2014-06-10  8:30 ` Jens Lucius
2014-06-10  8:53 ` Paul Eggleton [this message]
2014-06-10  8:58 ` Alex J Lennon
2014-06-11 15:04   ` Jim Rafert
2014-06-10 15:02 ` Maxim Radugin
2014-06-13 22:02 ` Jim Rafert

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=2167937.Ioj4ylAJNq@peggleto-mobl5.ger.corp.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=jimr@spectralogic.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.