All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rapidjson: new package
Date: Thu, 28 Mar 2013 14:15:27 +0100	[thread overview]
Message-ID: <20130328141527.0061ef53@skate> (raw)
In-Reply-To: <1364472920-11835-1-git-send-email-spdawson@gmail.com>

Simon,

On Thu, 28 Mar 2013 12:15:19 +0000, spdawson at gmail.com wrote:

> diff --git a/package/rapidjson/rapidjson.mk b/package/rapidjson/rapidjson.mk
> new file mode 100644
> index 0000000..cc260e9
> --- /dev/null
> +++ b/package/rapidjson/rapidjson.mk
> @@ -0,0 +1,34 @@
> +#############################################################
> +#
> +# rapidjson
> +#
> +#############################################################
> +
> +RAPIDJSON_VERSION = 0.11
> +RAPIDJSON_SOURCE = rapidjson-$(RAPIDJSON_VERSION).zip
> +RAPIDJSON_SITE = http://rapidjson.googlecode.com/files
> +RAPIDJSON_LICENSE = MIT
> +RAPIDJSON_LICENSE_FILES = license.txt
> +RAPIDJSON_INSTALL_TARGET = NO
> +RAPIDJSON_INSTALL_STAGING = YES

How does this thing work if you install only things in staging? Is it a
code generator that runs on the host? And if so, shouldn't some stuff
be installed in $(HOST_DIR) ?

Thanks,

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

  reply	other threads:[~2013-03-28 13:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 12:15 [Buildroot] [PATCH] rapidjson: new package spdawson at gmail.com
2013-03-28 13:15 ` Thomas Petazzoni [this message]
2013-03-28 13:26   ` Simon Dawson
2013-03-28 13:33     ` Thomas Petazzoni
2013-04-21 21:29 ` Peter Korsgaard

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=20130328141527.0061ef53@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.