From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] leptonica: new package
Date: Tue, 14 Mar 2017 21:34:31 +0100 [thread overview]
Message-ID: <20170314213431.53ef9c38@free-electrons.com> (raw)
In-Reply-To: <1489517067-3155-2-git-send-email-gilles.talis@gmail.com>
Hello,
On Tue, 14 Mar 2017 19:44:25 +0100, Gilles Talis wrote:
> Signed-off-by: Gilles Talis <gilles.talis@gmail.com>
> ---
> package/Config.in | 1 +
> package/leptonica/Config.in | 9 +++++++
> package/leptonica/leptonica.hash | 2 ++
> package/leptonica/leptonica.mk | 57 ++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 69 insertions(+)
The change to the DEVELOPERS file for that specific package should be
in this patch.
I know we asked to do things differently in the past (i.e have the
change to the DEVELOPERS in a separate commit), but we changed our
mind, and now want the DEVELOPERS change with the patch adding the
package.
> diff --git a/package/leptonica/Config.in b/package/leptonica/Config.in
> new file mode 100644
> index 0000000..d485344
> --- /dev/null
> +++ b/package/leptonica/Config.in
> @@ -0,0 +1,9 @@
> +config BR2_PACKAGE_LEPTONICA
> + bool "leptonica"
> +
Unneeded empty line.
There is no toolchain dependency? It builds fine with
uClibc/musl/glibc, noMMU, static libraries only, etc. ?
Could you test this package with support/scripts/test-pkg ?
> diff --git a/package/leptonica/leptonica.mk b/package/leptonica/leptonica.mk
> new file mode 100644
> index 0000000..5f2da79
> --- /dev/null
> +++ b/package/leptonica/leptonica.mk
> @@ -0,0 +1,57 @@
> +################################################################################
> +#
> +# leptonica
> +#
> +################################################################################
> +
> +LEPTONICA_VERSION = 1.74.1
> +LEPTONICA_SITE = http://www.leptonica.org/source
> +LEPTONICA_LICENSE = BSD-2c
> +LEPTONICA_LICENSE_FILES = leptonica-license.txt
OK, license verified, looks good to me.
> +LEPTONICA_INSTALL_STAGING = YES
> +
> +LEPTONICA_CONF_OPTS += --disable-programs
> +
> +ifeq ($(BR2_PACKAGE_GIFLIB),y)
> +LEPTONICA_DEPENDENCIES += giflib
Please explicitly pass:
LEPTONICA_CONF_OPTS += --with-giflib
here, and same for all other options below.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-14 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 18:44 [Buildroot] [PATCH 0/3] Introducing tesseract OCR engine package Gilles Talis
2017-03-14 18:44 ` [Buildroot] [PATCH 1/3] leptonica: new package Gilles Talis
2017-03-14 20:34 ` Thomas Petazzoni [this message]
2017-03-15 6:24 ` Gilles Talis
2017-03-14 18:44 ` [Buildroot] [PATCH 2/3] tesseract-ocr: " Gilles Talis
2017-03-14 20:41 ` Thomas Petazzoni
2017-03-15 6:32 ` Gilles Talis
2017-03-14 18:44 ` [Buildroot] [PATCH 3/3] DEVELOPERS: add leptonica and tesseract-ocr to my list Gilles Talis
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=20170314213431.53ef9c38@free-electrons.com \
--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