Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: Ross Burton <ross@burtonini.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] #yocto
Date: Tue, 20 Jul 2021 10:27:18 +0000	[thread overview]
Message-ID: <MADEUP.169378F95810F934.9501@lists.yoctoproject.org> (raw)
In-Reply-To: <CAAnfSTtAeE9YN8RrM0QyoYqtQaARLpUYmSAzj_+pe8YpU02rGw@mail.gmail.com>


Thanks...


-----Original Message-----
From: Ross Burton <ross@burtonini.com> 
Sent: Tuesday, July 20, 2021 5:03 AM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros.  For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.


Not deleting the source tree is the default behaviour.  It sounds like you've inherited rm_work, so if you want to not delete build trees after completion then add the recipe name to RM_WORK_EXCLUDE.

Ross

On Mon, 19 Jul 2021 at 15:22, Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@lists.yoctoproject.org> wrote:
>
>
>
> What flag do I set in order to keep the source code for a recipe being built within the build tree after compilation  ?
>
>
>
> Thanks,
>
> Steve
>
>
> 
>

  reply	other threads:[~2021-07-20 10:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 13:41 #yocto Monsees, Steven C (US)
2021-07-20  9:02 ` [yocto] #yocto Ross Burton
2021-07-20 10:27   ` Monsees, Steven C (US) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-23  6:26 #yocto sateesh m
2021-07-23  9:57 ` [yocto] #yocto Yocto
2021-07-27 10:48   ` sateesh m
2021-07-27 12:47 ` Nicolas Jeker
2021-07-27 15:18   ` sateesh m
2021-07-27 18:04 ` Khem Raj
     [not found] <1648FB72CE3E4F12.13688@lists.yoctoproject.org>
2020-12-01 20:06 ` Monsees, Steven C (US)
2020-12-02  9:21   ` Nicolas Jeker
2020-12-02 11:34     ` Monsees, Steven C (US)
2020-11-18 13:08 Monsees, Steven C (US)
2020-11-18 13:08 #yocto Monsees, Steven C (US)
2020-11-19  0:30 ` [yocto] #yocto Randy MacLeod
2020-11-19 12:03   ` Monsees, Steven C (US)
2020-11-19  0:30 ` Randy MacLeod
2020-10-29 19:37 #yocto Monsees, Steven C (US)
2020-10-29 19:47 ` [yocto] #yocto mail
2020-11-02 12:36   ` #yocto Monsees, Steven C (US)
2020-11-02 12:44     ` [yocto] #yocto Martin Jansa
2020-07-01 15:36 #yocto Pankaj  Vinadrao Joshi
2020-07-01 15:41 ` [yocto] #yocto Quentin Schulz
2020-07-01 16:04   ` #yocto Pankaj  Vinadrao Joshi
2020-07-01 19:29     ` [yocto] #yocto Tim Orling
2020-06-03 13:56 #yocto Baabu Ms
2020-06-03 14:00 ` [yocto] #yocto Quentin Schulz
     [not found] <rud8.1590333778048678194.rbAK@lists.yoctoproject.org>
2020-05-28 15:30 ` Khem Raj

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=MADEUP.169378F95810F934.9501@lists.yoctoproject.org \
    --to=steven.monsees@baesystems.com \
    --cc=ross@burtonini.com \
    --cc=yocto@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox