Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Interaction between SITE_METHOD=LOCAL and .patch files
Date: Wed, 8 Feb 2017 10:02:48 +0100	[thread overview]
Message-ID: <20170208100248.5fa0965d@free-electrons.com> (raw)
In-Reply-To: <87o9ydrdep.fsf@dell.be.48ers.dk>

Hello,

On Tue, 07 Feb 2017 20:47:42 +0100, Peter Korsgaard wrote:

>  > Is it just the .patch files found in the package directory that are
>  > skipped in the [FOO_SITE_METHOD = local] case?  Or are all patches
>  > skipped (also skipping those specified by FOO_PATCH and
>  > BR2_GLOBAL_PATCH_DIR)?  
> 
> All patches, it skips directly to to the configure step.

Just to clarify things:

 * For all site methods (except local/OVERRIDE_SRCDIR), the steps
   through which a package go are:

   source -> extract -> patch -> configure -> build -> install

 * For the local site method and OVERRIDE_SRCDIR, the steps through
   which a package go are:

   rsync -> configure -> build -> install

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-02-08  9:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 21:54 [Buildroot] Interaction between SITE_METHOD=LOCAL and .patch files Grant Edwards
2017-02-07 16:55 ` Arnout Vandecappelle
2017-02-07 17:18   ` Grant Edwards
2017-02-07 17:37     ` Grant Edwards
2017-02-07 19:47       ` Peter Korsgaard
2017-02-08  9:02         ` Thomas Petazzoni [this message]
2017-02-08  9:01     ` Thomas Petazzoni

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=20170208100248.5fa0965d@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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