From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libxmlrpc: new package
Date: Wed, 9 Oct 2013 13:43:55 +0200 [thread overview]
Message-ID: <20131009134355.44ae2733@skate> (raw)
In-Reply-To: <1381311986-11533-1-git-send-email-alvaro.gamez@hazent.com>
Dear Alvaro G. M,
On Wed, 9 Oct 2013 11:46:26 +0200, Alvaro G. M wrote:
> From: Alvaro G. M. <alvaro.gamez@hazent.com>
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: Alvaro G. M <alvaro.gamez@hazent.com>
> ---
>
> I recovered an old patch from Thomas (http://lists.busybox.net/pipermail/buildroot/2012-June/054467.html)
> and upgraded it to the stable version of xml-rpc-c.
> Some of the original patches are not needed on this version, so I've mostly just deleted
> a patch files, upgraded download address and version and modified patch offsets so they apply
> without any warning.
>
> package/Config.in | 1 +
> package/libxmlrpc/Config.in | 10 +++++++
> .../libxmlrpc/libxmlrpc-fix-gennmtab-build.patch | 25 ++++++++++++++++
> .../libxmlrpc-fix-non-cplusplus-build.patch | 27 +++++++++++++++++
> .../libxmlrpc/libxmlrpc-fix-non-wchar-build.patch | 24 +++++++++++++++
> .../libxmlrpc-use-correct-curl-config.patch | 22 ++++++++++++++
It would be good to use a number in the patch file names, such as:
libxmlrpc-01-<something>.patch
libxmlrpc-02-<somethingelse>.patch
> new file mode 100644
> index 0000000..ef41041
> --- /dev/null
> +++ b/package/libxmlrpc/libxmlrpc.mk
> @@ -0,0 +1,34 @@
> +#############################################################
Those lines should have 80 #
> +#
> +# libxmlrpc
> +#
> +#############################################################
One empty line between the header and the first variable.
> +LIBXMLRPC_VERSION = 1.25.26
> +LIBXMLRPC_SOURCE = xmlrpc-c-$(LIBXMLRPC_VERSION).tgz
> +LIBXMLRPC_SITE = "http://downloads.sourceforge.net/project/xmlrpc-c/Xmlrpc-c%20Super%20Stable/1.25.26"
> +LIBXMLRPC_INSTALL_STAGING = YES
> +LIBXMLRPC_DEPENDENCIES = libcurl
Can you add LIBXMLRPC_LICENSE and LIBXMLRPC_LICENSE_FILES ?
> +LIBXMLRPC_CONF_OPT = \
> + $(if $(BR2_USE_WCHAR),,ac_cv_header_wchar_h=no) \
> + $(if $(BR2_INSTALL_LIBSTDCPP),,--disable-cplusplus) \
> + have_curl_config=$(STAGING_DIR)/usr/bin/curl-config \
> + CURL_CONFIG=$(STAGING_DIR)/usr/bin/curl-config
> +
> +# Our package uses autoconf, but not automake, so we need to pass
> +# those variables at compile time as well.
> +LIBXMLRPC_MAKE_ENV = \
> + CC_FOR_BUILD="$(HOSTCC)" \
> + LD_FOR_BUILD="$(HOSTLD)" \
> + CFLAGS_FOR_BUILD="$(HOST_CFLAGS)" \
> + LDFLAGS_FOR_BUILD="$(HOST_LDFLAGS)"
> +
> +define LIBXMLRPC_REMOVE_DEVFILE
> + $(RM) $(TARGET_DIR)/usr/bin/xmlrpc-c-config
> +endef
Hum, maybe this should use the <pkg>_CONFIG_SCRIPTS mechanism instead
(if xmlrpc-c-config is a shell script).
> +
> +ifeq ($(BR2_HAVE_DEVFILES),)
> +LIBXMLRPC_POST_INSTALL_TARGET_HOOKS += LIBXMLRPC_REMOVE_DEVFILE
> +endif
> +
> +$(eval $(autotools-package))
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-09 11:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 16:13 [Buildroot] [pull request] Pull request for branch for-2012.08/new-packages Thomas Petazzoni
2012-06-02 16:13 ` [Buildroot] [PATCH 01/10] monit: new package Thomas Petazzoni
2012-06-11 20:31 ` Peter Korsgaard
2012-06-02 16:13 ` [Buildroot] [PATCH 02/10] libcurl: fix up prefix in curl-config Thomas Petazzoni
2012-06-11 20:36 ` Peter Korsgaard
2012-06-02 16:13 ` [Buildroot] [PATCH 03/10] libxmlrpc: new package Thomas Petazzoni
2012-06-04 23:58 ` Arnout Vandecappelle
2013-10-09 9:46 ` [Buildroot] [PATCH] " Alvaro G. M
2013-10-09 11:43 ` Thomas Petazzoni [this message]
2013-10-09 12:08 ` Alvaro Gamez
2013-10-09 12:16 ` Alvaro G. M
2013-10-09 13:09 ` Thomas De Schampheleire
2013-10-09 13:21 ` Alvaro Gamez
2013-10-09 13:46 ` Thomas De Schampheleire
2013-10-09 13:57 ` Alvaro Gamez
2013-10-09 13:58 ` Alvaro G. M
2013-10-09 14:09 ` Baruch Siach
2013-10-09 14:19 ` Alvaro G. M
2014-03-03 21:58 ` Thomas Petazzoni
2013-10-10 6:49 ` Arnout Vandecappelle
2013-10-10 7:47 ` Alvaro Gamez
[not found] ` <4FCD4B6D.3080506@mind.be>
2012-06-05 21:26 ` [Buildroot] [PATCH 03/10] " Thomas Petazzoni
2013-01-12 20:17 ` Peter Korsgaard
2013-01-13 14:08 ` Thomas Petazzoni
2013-01-13 16:10 ` Peter Korsgaard
2012-06-02 16:13 ` [Buildroot] [PATCH 04/10] llrp-toolkit: " Thomas Petazzoni
2012-06-02 16:13 ` [Buildroot] [PATCH 05/10] qextserialport: " Thomas Petazzoni
2012-11-03 18:18 ` Peter Korsgaard
2012-06-02 16:13 ` [Buildroot] [PATCH 06/10] pciutils: install headers and libraries in STAGING_DIR Thomas Petazzoni
2012-06-11 20:43 ` Peter Korsgaard
2012-06-02 16:13 ` [Buildroot] [PATCH 07/10] dmidecode: new package Thomas Petazzoni
2012-06-11 20:44 ` Peter Korsgaard
2012-06-02 16:13 ` [Buildroot] [PATCH 08/10] flashrom: " Thomas Petazzoni
2012-06-11 20:48 ` Peter Korsgaard
2012-06-02 16:13 ` [Buildroot] [PATCH 09/10] qt: make $(HOST_DIR)/usr/mkspecs a symlink to $(STAGING_DIR)/usr/mkspecs Thomas Petazzoni
2012-06-11 20:50 ` Peter Korsgaard
2012-06-02 16:14 ` [Buildroot] [PATCH 10/10] libqwt: new package Thomas Petazzoni
2012-09-10 9:06 ` Yegor Yefremov
2013-01-13 21:45 ` 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=20131009134355.44ae2733@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