Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][master-next][PATCH v3 00/17] rely on cmake.bbclass to put cmake package files in dev package
Date: Thu, 24 May 2018 10:38:37 -0400	[thread overview]
Message-ID: <20180524143854.24096-1-twoerner@gmail.com> (raw)

v3:
- break patches back up into individual patches for each recipe
- avoid including fftw
- find a couple extra recipes to patch:
	libwebsockets
	opencv
	libeigen

v2:
- re-spin Andre's patches to only include this change
  (i.e. rely on cmake.bbclass) without any formatting changes
- re-base on top of master-next (changes location of grpc)
- combine all such patches together into 2 patches
  (one for meta-oe, one for meta-networking)

v1:
- Andre's original patchset

Trevor Woerner (17):
  openobex: rely on cmake.bbclass to put cmake package files in dev package
  rocksdb: rely on cmake.bbclass to put cmake package files in dev package
  capnproto: rely on cmake.bbclass to put cmake package files in dev package
  json-spirit: rely on cmake.bbclass to put cmake package files in dev package
  librcf: rely on cmake.bbclass to put cmake package files in dev package
  msgpack_c: rely on cmake.bbclass to put cmake package files in dev package
  rapidjson: rely on cmake.bbclass to put cmake package files in dev package
  glm: rely on cmake.bbclass to put cmake package files in dev package
  openjpeg: rely on cmake.bbclass to put cmake package files in dev package
  ceres-solver: rely on cmake.bbclass to put cmake package files in dev package
  gflags: rely on cmake.bbclass to put cmake package files in dev package
  libftdi: rely on cmake.bbclass to put cmake package files in dev package
  libssh: rely on cmake.bbclass to put cmake package files in dev package
  libtinyxml2: rely on cmake.bbclass to put cmake package files in dev package
  libwebsockets: rely on cmake.bbclass to put cmake package files in dev package
  opencv: rely on cmake.bbclass to put cmake package files in dev package
  libeigen: rely on cmake.bbclass to put cmake package files in dev package

 .../recipes-connectivity/libwebsockets/libwebsockets_3.0.0.bb   | 1 -
 meta-oe/recipes-connectivity/obex/openobex_1.7.2.bb             | 2 +-
 meta-oe/recipes-dbs/rocksdb/rocksdb_git.bb                      | 2 --
 meta-oe/recipes-devtools/capnproto/capnproto_0.6.1.bb           | 1 -
 meta-oe/recipes-devtools/json-spirit/json-spirit_4.08.bb        | 2 --
 meta-oe/recipes-devtools/librcf/librcf_2.2.0.0.bb               | 1 -
 meta-oe/recipes-devtools/msgpack/msgpack-c_2.1.5.bb             | 2 --
 meta-oe/recipes-devtools/rapidjson/rapidjson_git.bb             | 1 -
 meta-oe/recipes-graphics/glm/glm_0.9.9-a2.bb                    | 1 -
 meta-oe/recipes-graphics/openjpeg/openjpeg_2.2.0.bb             | 2 --
 meta-oe/recipes-support/ceres-solver/ceres-solver_1.14.bb       | 2 --
 meta-oe/recipes-support/gflags/gflags_2.2.0.bb                  | 2 --
 meta-oe/recipes-support/libeigen/libeigen_3.3.4.bb              | 2 +-
 meta-oe/recipes-support/libftdi/libftdi_1.4.bb                  | 2 --
 meta-oe/recipes-support/libssh/libssh_0.7.3.bb                  | 1 -
 meta-oe/recipes-support/libtinyxml2/libtinyxml2_5.0.1.bb        | 2 --
 meta-oe/recipes-support/opencv/opencv_3.3.bb                    | 2 +-
 17 files changed, 3 insertions(+), 25 deletions(-)

-- 
2.17.0.582.gccdcbd54c



             reply	other threads:[~2018-05-24 14:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 14:38 Trevor Woerner [this message]
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 01/17] openobex: rely on cmake.bbclass to put cmake package files in dev package Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 02/17] rocksdb: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 03/17] capnproto: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 04/17] json-spirit: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 05/17] librcf: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 06/17] msgpack_c: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 07/17] rapidjson: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 08/17] glm: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 09/17] openjpeg: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 10/17] ceres-solver: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 11/17] gflags: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 12/17] libftdi: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 13/17] libssh: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 14/17] libtinyxml2: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 15/17] libwebsockets: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 16/17] opencv: " Trevor Woerner
2018-05-25  3:19   ` Anuj Mittal
2018-05-25 15:08     ` Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 17/17] libeigen: " Trevor Woerner
2018-05-25 15:22   ` Trevor Woerner
2018-05-25 19:58     ` Andre McCurdy
2018-05-26  2:45       ` Trevor Woerner
2018-05-26  2:49         ` Trevor Woerner
2018-05-29 19:55           ` Khem Raj

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=20180524143854.24096-1-twoerner@gmail.com \
    --to=twoerner@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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