All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/ti-gfx: do not forcefully remove source dir on extract
Date: Wed, 26 Feb 2014 22:50:38 +0100	[thread overview]
Message-ID: <530E61AE.6090707@mind.be> (raw)
In-Reply-To: <87bnxtczxi.fsf@dell.be.48ers.dk>

On 26/02/14 22:43, Peter Korsgaard wrote:
>>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> 
>  > On 26/02/14 19:40, Yann E. MORIN wrote:
>  >> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
>  >> 
>  >> ti-gfx uses custom extract commands, which first and foremost removes
>  >> the source dir unconditionally.
>  >> 
>  >> Thee side-effect of this is that make will re-extract, re-patch and
>  >> probably re-build ti-gfx at each run.
> 
>  >  There actually was a reason for this - I think the extract fails if you
>  > re-run it. Have you tried
> 
>  > make ti-gfx-extract; make ti-gfx-extract
> 
> That afaik simply says nothing to do, like it should.

 I mean if the stamp file is removed.

 But I realize now that this is something that doesn't necessarily work
anyway, so please ignore my comment.

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-02-26 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 18:40 [Buildroot] [PATCH] package/ti-gfx: do not forcefully remove source dir on extract Yann E. MORIN
2014-02-26 20:51 ` Peter Korsgaard
2014-02-26 21:33 ` Arnout Vandecappelle
2014-02-26 21:43   ` Peter Korsgaard
2014-02-26 21:50     ` Arnout Vandecappelle [this message]
2014-02-26 21:48   ` Yann E. MORIN

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=530E61AE.6090707@mind.be \
    --to=arnout@mind.be \
    --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 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.