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] [PATCH 1/1] capnproto: new package
Date: Fri, 7 Jul 2017 09:44:43 +0200	[thread overview]
Message-ID: <20170707094443.3de6a9e0@windsurf.lan> (raw)
In-Reply-To: <A9C99900-5E84-4FF4-9980-DBB39ED471AA@sonologic.nl>

Hello,

On Fri, 07 Jul 2017 08:58:08 +0200, Koen Martens wrote:

> >Since upstream uses Git, we prefer to have a Git-formatted patch, i.e
> >generated with "git format-patch -N". It should also have a proper
> >commit title, i.e a single line at the beginning that summarizes the
> >commit, separated from the rest of the commit log by one empty line.  
> 
> Sure, except the published tarball is from a subdirectory of the
> upstream git repo. So creating a git patch with format-patch results
> in a patch that needs 'patch -p2' to apply in buildroot. I understand
> this is impossible. What do you prefer i do? Manually modify the
> patch to remove the subdir that should be stripped?

Gah, OK. Then perhaps a quick comment in the patch description would be
nice, like:

[Patch cannot be generated with git format-patch, as the upstream Git
repository directory layout doesn't match the tarball directory layout]

> >> +CAPNPROTO_DEPENDENCIES = host-capnproto  
> >
> >Could you give some details as to why the host capnproto is necessary
> >to build the target capnproto ?  
> 
> Capnproto provides a compiler to compile capnproto message
> definitions to c++ code. The library uses capnproto messages itself,
> and thus needs the capnproto compiler to compile. This obviously must
> be the host capnproto compiler, because the target compiler will not
> run on the compiling host.
> 
> Is that sufficient detail, or do you want this in the package files
> somewhere? If so, where?

A quick comment above the dependency would be nice, like:

# Needs the capnproto compiler on the host to generate C++ code from
# message definitions

Thanks!

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

  reply	other threads:[~2017-07-07  7:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 15:40 [Buildroot] [PATCH 1/1] capnproto: new package Koen Martens
2017-07-06 19:16 ` Thomas Petazzoni
2017-07-07  6:58   ` Koen Martens
2017-07-07  7:44     ` Thomas Petazzoni [this message]
2017-07-07 17:39       ` Koen Martens
2017-07-07 18:16         ` Thomas Petazzoni
2017-07-07 18:29           ` Koen Martens
2017-07-06 22:44 ` Arnout Vandecappelle

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=20170707094443.3de6a9e0@windsurf.lan \
    --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