All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Vuille, Martin (Martin)" <vmartin@avaya.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: populate_sysroot and sstate question
Date: Wed, 25 Mar 2015 13:51:22 +0000	[thread overview]
Message-ID: <1427291482.14020.42.camel@linuxfoundation.org> (raw)
In-Reply-To: <30C2D590D16A5C46ADFE652191037798538ED580@AZ-US1EXMB03.global.avaya.com>

On Wed, 2015-03-25 at 13:33 +0000, Vuille, Martin (Martin) wrote:
> > From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org]
> > Sent: March 25, 2015 9:09 AM
> > 
> > On Tue, 2015-03-24 at 22:22 +0000, Vuille, Martin (Martin) wrote:
> > > Is there a better way to suppress populate_sysroot without breaking
> > > setscene?
> > 
> > Define an empty sysroot_stage_dirs function.
> > 
> 
> Thanks Richard, but I still get the same error, see below. Perhaps I misunderstood
> your instructions.
> 
> I did a cleansstate on the package, added the empty function to the recipe
> 
> 	do_populate_sysroot () {
> 	}
> 
> 	sysroot_stage_dirs() {
> 	}

Just define the empty sysroot_stage_dirs, not populate_sysroot. The
stage_dirs function handles copying files so if its empty, no files will
be copied in.

Cheers,

Richard



  reply	other threads:[~2015-03-25 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 22:22 populate_sysroot and sstate question Vuille, Martin (Martin)
2015-03-25 13:08 ` Richard Purdie
2015-03-25 13:33   ` Vuille, Martin (Martin)
2015-03-25 13:51     ` Richard Purdie [this message]
2015-03-25 14:48       ` Vuille, Martin (Martin)

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=1427291482.14020.42.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=vmartin@avaya.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.