[meta-oe][PATCH] ceres-solver: add new recipe

[meta-oe][PATCH] ceres-solver: add new recipe

[Bartosz Golaszewski]

From: Bartosz Golaszewski <brgl+baylibre@bgdev.pl>

Ceres Solver is an open source C++ library for modeling and solving
large, complicated optimization problems.

It's often used in 3D computer vision applications.

Signed-off-by: Bartosz Golaszewski <brgl+baylibre@bgdev.pl>
---
 .../recipes-support/ceres-solver/ceres-solver_1.13.bb  | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 meta-oe/recipes-support/ceres-solver/ceres-solver_1.13.bb

diff --git a/meta-oe/recipes-support/ceres-solver/ceres-solver_1.13.bb b/meta-oe/recipes-support/ceres-solver/ceres-solver_1.13.bb
new file mode 100644
index 0000000..0bfc083
--- /dev/null
+++ b/meta-oe/recipes-support/ceres-solver/ceres-solver_1.13.bb
@@ -0,0 +1,18 @@
+DESCRIPTION = "Ceres Solver is an open source C++ library for modeling and solving large, complicated optimization problems."
+AUTHOR = "Sameer Agarwal and Keir Mierle and Others"
+HOMEPAGE = "http://ceres-solver.org/"
+
+LICENSE = "BSD-3-Clause"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=35e00f0c4c96a0820a03e0b31e6416be"
+
+SRC_URI = "https://github.com/ceres-solver/ceres-solver/archive/${PV}.tar.gz"
+SRC_URI[md5sum] = "810f53772be2c41abff53a9c03d1e301"
+SRC_URI[sha256] = "51ccb201b61ac71501fb6ccef158f078a750bc796ee6a271cd535cfe338202e5"
+
+PV = "1.13.0"
+
+DEPENDS = "libeigen glog"
+
+inherit cmake
+
+FILES_${PN} = "${includedir} ${libdir}"
-- 
2.7.4

Re: [meta-oe][PATCH] ceres-solver: add new recipe

[Martin Jansa]

Don't use github archives as they might get regenerated from time to time.

Why do you set PV in the recipe to 1.13.0 and the filename 1.13? Use just
one.

The FILES variable look suspicious, why are you trying to include whole
libdir and includedir? Most of it will be packaged in PN-dev anyway.

On Wed, Sep 13, 2017 at 1:04 PM, Bartosz Golaszewski <brgl@bgdev.pl> wrote:

> From: Bartosz Golaszewski <brgl+baylibre@bgdev.pl>
>
> Ceres Solver is an open source C++ library for modeling and solving
> large, complicated optimization problems.
>
> It's often used in 3D computer vision applications.
>
> Signed-off-by: Bartosz Golaszewski <brgl+baylibre@bgdev.pl>
> ---
>  .../recipes-support/ceres-solver/ceres-solver_1.13.bb  | 18
> ++++++++++++++++++
>  1 file changed, 18 insertions(+)
>  create mode 100644 meta-oe/recipes-support/ceres-solver/
> ceres-solver_1.13.bb
>
> diff --git a/meta-oe/recipes-support/ceres-solver/ceres-solver_1.13.bb
> b/meta-oe/recipes-support/ceres-solver/ceres-solver_1.13.bb
> new file mode 100644
> index 0000000..0bfc083
> --- /dev/null
> +++ b/meta-oe/recipes-support/ceres-solver/ceres-solver_1.13.bb
> @@ -0,0 +1,18 @@
> +DESCRIPTION = "Ceres Solver is an open source C++ library for modeling
> and solving large, complicated optimization problems."
> +AUTHOR = "Sameer Agarwal and Keir Mierle and Others"
> +HOMEPAGE = "http://ceres-solver.org/"
> +
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=35e00f0c4c96a0820a03e0b31e6416be"
> +
> +SRC_URI = "https://github.com/ceres-solver/ceres-solver/archive/${
> PV}.tar.gz"
> +SRC_URI[md5sum] = "810f53772be2c41abff53a9c03d1e301"
> +SRC_URI[sha256] = "51ccb201b61ac71501fb6ccef158f0
> 78a750bc796ee6a271cd535cfe338202e5"
> +
> +PV = "1.13.0"
> +
> +DEPENDS = "libeigen glog"
> +
> +inherit cmake
> +
> +FILES_${PN} = "${includedir} ${libdir}"
> --
> 2.7.4
>
>

Re: [meta-oe][PATCH] ceres-solver: add new recipe

[Bartosz Golaszewski]

2017-09-13 13:39 GMT+02:00 Martin Jansa <martin.jansa@gmail.com>:
> Don't use github archives as they might get regenerated from time to time.
>

What do I calculate the checksums from when not using tarballs?

Best regards,
Bartosz Golaszewski

Re: [meta-oe][PATCH] ceres-solver: add new recipe

[Martin Jansa]

git fetcher doesn't use SRC_URI checksums, just SRCREV

On Wed, Sep 13, 2017 at 1:48 PM, Bartosz Golaszewski <brgl@bgdev.pl> wrote:

> 2017-09-13 13:39 GMT+02:00 Martin Jansa <martin.jansa@gmail.com>:
> > Don't use github archives as they might get regenerated from time to
> time.
> >
>
> What do I calculate the checksums from when not using tarballs?
>
> Best regards,
> Bartosz Golaszewski
>