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] New package protobuf
Date: Fri, 9 Mar 2012 09:16:23 +0100	[thread overview]
Message-ID: <20120309091623.64bac36d@skate> (raw)
In-Reply-To: <CAHt8ZCPFyS15PPKmQtWAaFNpDw4JKNvfFZgWegAJoA8v1GYxQw@mail.gmail.com>

Hello Simon,

Le Wed, 7 Mar 2012 21:14:13 +0000,
Simon Dawson <spdawson@gmail.com> a ?crit :

> Thanks for your comments; re-worked patch attached below.

Please do not include "personal" comments before the "---", because
everything before "---" will end up as the commit log in the Git
history of Buildroot. So everything before "---" should be a nice
commit message, and should not contain any sort of discussion about the
patch. If you want to put some discussion about the patch, put it
between the --- delimiter and the beginning of the patch itself.

> Both a utility (/usr/bin/protoc, the protocol buffers compiler) and a
> set of libraries (/usr/lib/libproto*.so) are installed on the target.

My guess is that the protocol buffer compiler is useless on the target,
no? Normally, you would :

 * Write a protocol buffer description file

 * Generate some code from it, using protoc on the host

 * Compile your application (which includes the generated code) for the
   target

And the libraries, are they useful on the target? I.e, does the code
generated by protoc depends on the libraries? If so, you should set
PROTOBUF_INSTALL_STAGING = YES in your package.

Can you clarify a bit the usage of the compiler vs. the libraries?

> diff --git a/package/protobuf/protobuf.mk
> b/package/protobuf/protobuf.mk new file mode 100644
> index 0000000..f4d82cb
> --- /dev/null
> +++ b/package/protobuf/protobuf.mk
> @@ -0,0 +1,15 @@
> +#############################################################
> +#
> +# protobuf
> +#
> +#############################################################
> +PROTOBUF_VERSION := 2.4.1
> +PROTOBUF_SOURCE := protobuf-$(PROTOBUF_VERSION).tar.gz
> +PROTOBUF_SITE := http://protobuf.googlecode.com/files/
> +
> +# N.B. Need to use host protoc during cross compilation.
> +PROTOBUF_DEPENDENCIES := host-protobuf
> +PROTOBUF_CONF_OPT := --with-protoc=$(HOST_DIR)/usr/bin/protoc

Please use = instead of := everywhere.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-03-09  8:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 18:06 [Buildroot] New package protobuf Simon Dawson
2012-03-07 19:23 ` Thomas Petazzoni
2012-03-07 21:14   ` Simon Dawson
2012-03-09  8:16     ` Thomas Petazzoni [this message]
2012-03-09 11:27       ` Simon Dawson

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=20120309091623.64bac36d@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