From: Tino Breddin <tb@travelping.com>
To: Jerrod Peach <peachj@lexmark.com>
Cc: yocto <yocto@yoctoproject.org>
Subject: Re: How to update Git clone when rebuilding
Date: Thu, 20 Dec 2012 17:03:26 +0100 [thread overview]
Message-ID: <50D336CE.6060706@travelping.com> (raw)
In-Reply-To: <CA+QkY1Dt0tYj+iREYRNVGXsMmiuxBRMBpc1i9pZDatjjcYxSDw@mail.gmail.com>
Hi Jerrod,
That looks promising. Will try that once I can build again.
Thanks,
Tino
On 12/20/2012 04:38 PM, Jerrod Peach wrote:
> Tino,
>
> SRCREV = "${AUTOREV}"
>
> You can read a little more about that in these two docs:
>
> http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-variables-glossary
> http://www.yoctoproject.org/docs/1.3/dev-manual/dev-manual.html#platdev-appdev-srcrev
>
> Kind regards,
>
> Jerrod
>
>
> On Thu, Dec 20, 2012 at 10:34 AM, Tino Breddin <tb@travelping.com> wrote:
>
>> Hi,
>>
>> I've noticed that bitbake won't update a Git checkout of an
>> application referenced through a recipe when running a follow-up build.
>>
>> Is there some way to tell bitbake to check whether the remote Git
>> repository provides updates which should trigger a rebuild of the
>> application?
>>
>> Cheers,
>> Tino
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
--
Tino Breddin
Technical Director
email: tb@travelping.com
mobile: +49-151-27054995
------------------- enabling your networks -------------------
Travelping GmbH phone: +49-391-819099229
Roentgenstr. 13 fax: +49-391-819099299
D-39108 Magdeburg email: info@travelping.com
GERMANY web: http://www.travelping.com
Company Registration: Amtsgericht Stendal Reg No.: HRB 10578
Geschaeftsfuehrer: Holger Winkelmann | VAT ID No.: DE236673780
--------------------------------------------------------------
prev parent reply other threads:[~2012-12-20 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 15:34 How to update Git clone when rebuilding Tino Breddin
2012-12-20 15:38 ` Jerrod Peach
2012-12-20 16:03 ` Tino Breddin [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=50D336CE.6060706@travelping.com \
--to=tb@travelping.com \
--cc=peachj@lexmark.com \
--cc=yocto@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 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.