mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Aring <alex.aring@gmail.com>
Subject: Re: [ptxdist] [PATCH] libcoap: add libcoap package
Date: Mon, 12 Aug 2013 19:02:16 +0200	[thread overview]
Message-ID: <52091518.1010108@pengutronix.de> (raw)
In-Reply-To: <1375432732-12559-1-git-send-email-alex.aring@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2352 bytes --]

On 08/02/2013 10:38 AM, Alexander Aring wrote:
> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> ---
>  ...ap-enable-shared-lib-and-install-examples.patch | 109 +++++++++++++++++++++
>  patches/libcoap-4.0.1/series                       |   1 +
>  rules/libcoap.in                                   |  10 ++
>  rules/libcoap.make                                 |  61 ++++++++++++
>  4 files changed, 181 insertions(+)
>  create mode 100644 patches/libcoap-4.0.1/0001-libcoap-enable-shared-lib-and-install-examples.patch
>  create mode 100644 patches/libcoap-4.0.1/series
>  create mode 100644 rules/libcoap.in
>  create mode 100644 rules/libcoap.make
> 
> diff --git a/patches/libcoap-4.0.1/0001-libcoap-enable-shared-lib-and-install-examples.patch b/patches/libcoap-4.0.1/0001-libcoap-enable-shared-lib-and-install-examples.patch
> new file mode 100644
> index 0000000..71c36c8
> --- /dev/null
> +++ b/patches/libcoap-4.0.1/0001-libcoap-enable-shared-lib-and-install-examples.patch
> @@ -0,0 +1,109 @@
> +From fe64f998eeb5d2a693400188b275007ce263fc87 Mon Sep 17 00:00:00 2001
> +From: unknown author <unknown.author@example.com>

Who created the patch in the first place?

> +Date: Fri, 2 Aug 2013 10:25:26 +0200
> +Subject: [PATCH] libcoap: enable shared lib and install examples
> +
> +Normally the buildsystem generates a static library.
> +This patch let generate the buildsystem a shared library and add
> +a install rule to the Makefile so we can install it on the system.
> +
> +Add also install rule for the examples and linking to the shared library.
> +
> +Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> +---
> + Makefile.in          | 21 +++++++++++++++++----
> + examples/Makefile.in |  7 ++++++-
> + 2 files changed, 23 insertions(+), 5 deletions(-)
> +
> +diff --git a/Makefile.in b/Makefile.in
> +index 0ded496..21564aa 100644
> +--- a/Makefile.in
> ++++ b/Makefile.in

Argh, autoconf without automake. Not your fault

...

What about creating a proper automake'd version of libcoap?

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-08-12 17:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  8:38 Alexander Aring
2013-08-12 17:02 ` Marc Kleine-Budde [this message]
2013-08-15  6:25   ` Alexander Aring
2013-08-15  8:16     ` Marc Kleine-Budde
2013-08-15  8:28       ` Alexander Aring
2013-08-15  9:24         ` Marc Kleine-Budde

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=52091518.1010108@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=alex.aring@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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