mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Enrico Joerns <ejo@pengutronix.de>
To: "Yazdani, Reyhaneh" <RYazdani@data-modul.com>
Cc: "meta-rauc@pengutronix.de" <meta-rauc@pengutronix.de>
Subject: Re: [meta-rauc] Source of RAUC in build directory
Date: Wed, 18 Sep 2019 11:04:18 +0200	[thread overview]
Message-ID: <74234caf-05f4-9860-4d75-73b1199446f1@pengutronix.de> (raw)
In-Reply-To: <997c186c-ec95-0e64-7726-b6ed7cbeee9f@data-modul.com>

Hi 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.
> 
> It is strange, although in all RAUC-recipes, SRC_URI is set to the github, it
> means I should see the downloaded source in my build directory.
> 
> does anyone have an idea? How can I apply my patch to the RAUC?

by default you should find the source in the work directory which is something like

   tmp/work/<architecture>/rauc/1.1-r0/rauc-1.1/

However, the sources won't be present if you build with having rm_work[1] enabled.

The simplest way to modify rauc out of Yocto is to use the 'devtool' [2]

   devtool modify rauc

which will create a 'workspace' layer and unpack the sources, etc. there.
You can also automatically create patches from this or deploy the updated tool 
to the target via ssh.


Best regards

Enrico


Note: To receive updates from this mailing list and to send mails without ending 
up in the moderation queue, consider subscribing [3] to it.


[1] 
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-classes-rm-work
[2] 
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-devtool-reference
[3] mailto:rauc-request@pengutronix.de?subject=subscribe

-- 
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

      parent reply	other threads:[~2019-09-18  9:04 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
2019-09-18  9:24     ` Yazdani, Reyhaneh
2019-09-18  9:04 ` Enrico Joerns [this message]

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=74234caf-05f4-9860-4d75-73b1199446f1@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=RYazdani@data-modul.com \
    --cc=meta-rauc@pengutronix.de \
    --subject='Re: [meta-rauc] Source of RAUC in build directory' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox