mail archive of the meta-rauc mailing list
 help / color / mirror / Atom feed
From: Enrico Joerns <ejo@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "Yazdani, Reyhaneh" <RYazdani@data-modul.com>,
	"meta-rauc@pengutronix.de" <meta-rauc@pengutronix.de>
Subject: Re: [meta-rauc] Source of RAUC in build directory
Date: Wed, 18 Sep 2019 11:05:33 +0200	[thread overview]
Message-ID: <10b41ac8-1998-fb59-286c-0dbce2856657@pengutronix.de> (raw)
In-Reply-To: <fe8610d9-cc09-1396-c5a0-2d14a68a6c2d@pengutronix.de>

On 9/18/19 11:02 AM, Ahmad Fatoum wrote:
> Hello Reyhaneh,
> 
> On 9/18/19 10:25 AM, Yazdani, Reyhaneh wrote:
>> Hello everyone,
>>
>> I am working to use RAUC in our system as updating framework. I am using
>> meta-rauc layer in yocto and everything works correctly.
>>
>> The point is, now I want to do some changes in Rauc and I cannot find any source
>> of it in my build directory! It is only the compiled files.
> 
> Do you have RM_WORK enabled by chance?
> That would clean up the directory when it's no longer needed.
> 
> There's also a devtool program that comes with bitbake that's quite useful for
> such things.

Oh, you were faster than me :D

Enrico

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


_______________________________________________
meta-rauc mailing list

  reply	other threads:[~2019-09-18  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18  8:25 Yazdani, Reyhaneh
2019-09-18  9:02 ` Ahmad Fatoum
2019-09-18  9:05   ` Enrico Joerns [this message]
2019-09-18  9:24     ` Yazdani, Reyhaneh
2019-09-18  9:04 ` Enrico Joerns

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=10b41ac8-1998-fb59-286c-0dbce2856657@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=RYazdani@data-modul.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=meta-rauc@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox