All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianfranco Costamagna <costamagna.gianfranco@gmail.com>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 2/2] cpprest: add new recipe based on Debian packaging
Date: Thu, 19 Apr 2018 17:44:46 +0200	[thread overview]
Message-ID: <CAATN8PXQ5ftKQCF8ZmWxdb92sst0AAZ3QMK7HMS4WRtqP9gv8w@mail.gmail.com> (raw)
In-Reply-To: <CALbNGRT17R_aw7NGTGo7_n6dY5ULsppkoE=OKfTJxC+vDESweg@mail.gmail.com>

Hello,

I prefer whenever possible to fix upstream defaults instead of downstream
patching.
My goal is to drop this patch on next upstream release, rather than
hardcoding a path in the bb file.

https://github.com/Microsoft/cpprestsdk/pull/737

I already opened an upstream pull request.

G.

2018-04-19 16:43 GMT+02:00 Andreas Müller <schnitzeltony@gmail.com>:

> On Thu, Apr 19, 2018 at 4:17 PM, Gianfranco Costamagna
> <costamagna.gianfranco@gmail.com> wrote:
> > Signed-off-by: Gianfranco Costamagna <locutusofborg@debian.org>
> > Signed-off-by: Gianfranco Costamagna <gianfranco.costamagna@abinsula.com
> >
> > Co-developed-by: Cristiano Prato <cristiano.prato@cnhind.com>
> > ---
> >  .../cpprest/cpprest-2.10.2/fix-cmake-install.patch    | 15
> +++++++++++++++
> >  meta-oe/recipes-support/cpprest/cpprest_2.10.2.bb     | 19
> +++++++++++++++++++
> >  2 files changed, 34 insertions(+)
> >  create mode 100644 meta-oe/recipes-support/cpprest/cpprest-2.10.2/fix-
> cmake-install.patch
> >  create mode 100644 meta-oe/recipes-support/cpprest/cpprest_2.10.2.bb
> >
> > diff --git a/meta-oe/recipes-support/cpprest/cpprest-2.10.2/fix-cmake-install.patch
> b/meta-oe/recipes-support/cpprest/cpprest-2.10.2/fix-cmake-install.patch
> > new file mode 100644
> > index 000000000..aeb8da052
> > --- /dev/null
> > +++ b/meta-oe/recipes-support/cpprest/cpprest-2.10.2/fix-
> cmake-install.patch
> > @@ -0,0 +1,15 @@
> > +Description: install cmake files into /usr/lib/cmake/cpprestsdk
> > +Author: Gianfranco Costamagna <locutusofborg@debian.org>
> > +Last-Update: 2018-04-19
> > +
> > +--- cpprest-2.10.2.orig/CMakeLists.txt
> > ++++ cpprest-2.10.2/CMakeLists.txt
> > +@@ -18,7 +18,7 @@ enable_testing()
> > + set(WERROR ON CACHE BOOL "Treat Warnings as Errors.")
> > + set(CPPREST_EXCLUDE_WEBSOCKETS OFF CACHE BOOL "Exclude websockets
> functionality.")
> > + set(CPPREST_EXCLUDE_COMPRESSION OFF CACHE BOOL "Exclude compression
> functionality.")
> > +-set(CPPREST_EXPORT_DIR lib/cpprestsdk CACHE STRING "Directory to
> install CMake config files.")
> > ++set(CPPREST_EXPORT_DIR lib/cmake/cpprestsdk CACHE STRING "Directory to
> install CMake config files.")
> ^ Instead of patching (for mulitlib?): Why not use this option? Something
> like
>
> EXTRA_OECMAKE = "-DCPPREST_EXPORT_DIR=${baselib}/cpprestsdk"
>
> > + set(CPPREST_INSTALL_HEADERS ON CACHE BOOL "Install header files.")
> > + set(CPPREST_INSTALL ON CACHE BOOL "Add install commands.")
> > +
> > diff --git a/meta-oe/recipes-support/cpprest/cpprest_2.10.2.bb
> b/meta-oe/recipes-support/cpprest/cpprest_2.10.2.bb
> > new file mode 100644
> > index 000000000..5f19d14ae
> > --- /dev/null
> > +++ b/meta-oe/recipes-support/cpprest/cpprest_2.10.2.bb
> > @@ -0,0 +1,19 @@
> > +SUMMARY = "Microsoft project for cloud-based client-server
> communication in native code using a modern asynchronous C++ API design."
> > +SECTION = "libs/network"
> > +HOMEPAGE = "https://github.com/Microsoft/cpprestsdk/"
> > +LICENSE = "MIT"
> > +LIC_FILES_CHKSUM = "file://${S}/../license.txt;md5=
> a2e15b954769218ff912468eecd6a02f"
> > +DEPENDS = "openssl websocketpp zlib boost"
> > +
> > +SRC_URI = "git://github.com/Microsoft/cpprestsdk.git;protocol=https;
> branch=master"
> > +
> > +SRC_URI += "file://fix-cmake-install.patch"
> > +
> > +# tag 2.10.2
> > +SRCREV= "fea848e2a77563cf2a6f28f8eab396fd6e787fbf"
> > +
> > +S = "${WORKDIR}/git/Release"
> > +
> > +inherit cmake
> > +
> > +FILES_${PN}-dev += "${libdir}/cmake"
> > --
> > 2.14.1
> >
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>


  reply	other threads:[~2018-04-19 15:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 14:17 [meta-oe][PATCH 1/2] websocketpp: add new recipe based on Debian packaging Gianfranco Costamagna
2018-04-19 14:17 ` [meta-oe][PATCH 2/2] cpprest: " Gianfranco Costamagna
2018-04-19 14:43   ` Andreas Müller
2018-04-19 15:44     ` Gianfranco Costamagna [this message]
2018-04-19 16:45       ` Andreas Müller
2018-04-19 17:12         ` Gianfranco Costamagna
2018-04-19 14:42 ` [meta-oe][PATCH 1/2] websocketpp: " Burton, Ross
2018-04-19 15:48   ` Gianfranco Costamagna
  -- strict thread matches above, loose matches on Subject: below --
2018-04-19 17:12 Gianfranco Costamagna
2018-04-19 17:12 ` [meta-oe][PATCH 2/2] cpprest: " Gianfranco Costamagna
2018-04-28 16:53   ` akuster808
2018-04-19 15:49 [meta-oe][PATCH 1/2] websocketpp: " Gianfranco Costamagna
2018-04-19 15:49 ` [meta-oe][PATCH 2/2] cpprest: " Gianfranco Costamagna
2018-04-19 12:04 [meta-oe][PATCH 1/2] websocketpp: " Gianfranco Costamagna
2018-04-19 12:04 ` [meta-oe][PATCH 2/2] cpprest: " Gianfranco Costamagna
2018-04-19 12:30   ` Anuj Mittal

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=CAATN8PXQ5ftKQCF8ZmWxdb92sst0AAZ3QMK7HMS4WRtqP9gv8w@mail.gmail.com \
    --to=costamagna.gianfranco@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=schnitzeltony@gmail.com \
    /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.