From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Is it possible to override a package from git?
Date: Wed, 09 Jul 2014 09:33:07 +0200 [thread overview]
Message-ID: <53BCF033.8050006@lucaceresoli.net> (raw)
In-Reply-To: <CAFRxoJ=iMsDdd3x5bGxkoyQ=rmeEMUKVaaBEOA16Kt8FBWc89w@mail.gmail.com>
Dear Marco,
Marco Pastorelli wrote:
> Hi everybody,
>
> I fetch my personal packages from my git repo specifying the tag.
> Now I would like to set up a nightly build system, so I need to download
> the HEAD of my packages repo instead of a specific tag.
>
> Is there a way to override the tag?
You can, although this requires some manual tweaking because it is not
typical.
It is not typical because Buildroot is generally meant to perform
reproducible builds. So it is usual to fetch a tag or SHA-1 from git
repos.
However in a nightly build system it can make sense.
To do that, you should set <MYPKG>_VERSION to a branch name. For
example <MYPKG>_VERSION=master.
You can do it also on the command line, without touching your source
code:
make my_defconfig
make <MYPKG>_VERSION=master
This will fetch the top of the master branch, not a specific tag.
However, when you build the next time, Buildroot will already find
<mypkg>-master.tar.gz in the downloaded sourced directory and will not
download it again. So before building you have to remove that archive
(or the whole download directory).
You'll also need to remove the output/build/<mypkg>-master/ directory,
or Buildroot will think it already has the sources for the "master"
version extracted and won't extract them again.
In a nutshell, if you're building in-tree:
rm -f <my_download_dir>/<mypkg>-master.tar.gz [*]
make my_defconfig
make <MYPKG>_VERSION=master <mypkg>-dirclean all
--
Luca
next prev parent reply other threads:[~2014-07-09 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 7:13 [Buildroot] Is it possible to override a package from git? Marco Pastorelli
2014-07-09 7:33 ` Luca Ceresoli [this message]
2014-07-09 9:05 ` Jérôme Pouiller
2014-07-09 14:55 ` Marco Pastorelli
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=53BCF033.8050006@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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