From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] package: Redownload HEAD packages every build
Date: Tue, 1 Oct 2013 23:37:39 +0200 [thread overview]
Message-ID: <20131001233739.618eb9f0@skate> (raw)
In-Reply-To: <OF074BC262.DC488FB4-ON86257BF7.006D21D1-86257BF7.006DFBEC@rockwellcollins.com>
Hello,
On Tue, 1 Oct 2013 15:01:52 -0500, clshotwe at rockwellcollins.com wrote:
> > It seems like the mechanism you're proposing overlaps quite
> > significantly with that, while being a bit less flexible. Have you
> > tried the <pkg>_OVERRIDE_SRCDIR mechanism?
>
> I did a little digging into the <pkg>_OVERRIDE_SRCDIR mechanism but I
> could not find any documentation and the implementation in the make
> structure is a little unclear. What is the full intent of that mechanism?
Either in your package .mk file or in a local.mk file, you can add:
FOO_OVERRIDE_SRCDIR = /path/to/foo/sources/
If you do that, then Buildroot will no longer download/extract/patch
the sources for the foo package, it will directly assume the sources
are located in /path/to/foo/sources/. It will rsync them to the build
directory, and build from there. Whenever you do:
make foo-reconfigure
or
make foo-rebuild
Buildroot will rsync again the source code, and restart the build at
the configuration step, or the build step of the foo package.
Usually, /path/to/foo/sources/ will be the directory where you did your
Subversion checkout or Git clone of your "foo" source code.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-01 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 14:43 [Buildroot] [RFC] package: Redownload HEAD packages every build Clayton Shotwell
2013-09-27 14:51 ` Clayton Shotwell
2013-09-27 15:11 ` Thomas De Schampheleire
2013-10-01 16:08 ` Arnout Vandecappelle
2013-10-01 18:51 ` Thomas Petazzoni
2013-10-01 20:01 ` clshotwe at rockwellcollins.com
2013-10-01 21:37 ` Thomas Petazzoni [this message]
2013-10-01 21:54 ` Ryan Barnett
2013-10-02 7:13 ` Thomas Petazzoni
2013-10-02 18:34 ` clshotwe at rockwellcollins.com
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=20131001233739.618eb9f0@skate \
--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