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] problem adding new package libcapn
Date: Tue, 16 Feb 2016 22:45:43 +0100	[thread overview]
Message-ID: <20160216224543.6a2a3558@free-electrons.com> (raw)
In-Reply-To: <56C3970E.5090405@mind.be>

Hello,

On Tue, 16 Feb 2016 22:39:26 +0100, Arnout Vandecappelle wrote:

> > 1) I am not sure how the git submodule update --init is handled in buildroot.
> 
>  If you need it, then you have to:
> 
> - add an EXTRA_DOWNLOADS of the tarball (using the github macro);
> 
> - add a POST_EXTRACT_HOOKS to extract the tarball in the right subdirectory.

I have the impression that this 'git submodule' thing is used more and
more, and that Buildroot not having support to automatically fetch
submodules is causing troubles to a number of people.

Not later than today, a colleague of mine also asked me about this,
since he is packaging something that uses submodules.

But very often, submodules are used to "bundle" libraries that should
rather be packaged as separate packages.

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

  reply	other threads:[~2016-02-16 21:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 23:01 [Buildroot] problem adding new package libcapn Johan Sagaert
2016-02-14 23:26 ` Johan Sagaert
2016-02-16 21:39 ` Arnout Vandecappelle
2016-02-16 21:45   ` Thomas Petazzoni [this message]
2016-02-17  0:28     ` Arnout Vandecappelle
2016-02-17  8:36       ` 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=20160216224543.6a2a3558@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