Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] imagemagick depends on pango even if not available
Date: Thu, 6 Aug 2015 22:48:29 +0200	[thread overview]
Message-ID: <20150806224829.61effbfa@free-electrons.com> (raw)
In-Reply-To: <55C3A446.8080307@mclink.it>

Dear Mauro Condarelli,

Thanks for your contribution! See below for some comments/questions.

On Thu, 6 Aug 2015 20:15:34 +0200, Mauro Condarelli wrote:
> Hi,
> it seems imagemagick package does not force dependency on pango, but fails if it's not found.

Can you give more details on how it fails?

> $ git diff
> diff --git a/package/imagemagick/imagemagick.mk b/package/imagemagick/imagemagick.mk
> index 1594f69..e8c7ab7 100644
> --- a/package/imagemagick/imagemagick.mk
> +++ b/package/imagemagick/imagemagick.mk
> @@ -44,6 +44,13 @@ else
>   IMAGEMAGICK_CONF_OPTS += --without-fontconfig
>   endif
> 
> +ifeq ($(BR2_PACKAGE_PANGO),y)
> +IMAGEMAGICK_CONF_OPTS += --with-pango
> +IMAGEMAGICK_DEPENDENCIES += pango
> +else
> +IMAGEMAGICK_CONF_OPTS += --without-pango
> +endif

This patch is not making pango a mandatory dependency of imagemagick.
It only makes it an optional dependency;

Again, can you give more details about the problem you're seeing?

The patch looks good (i.e pango is an optional dependency of
imagemagick), but the description is not. Can you clarify?

Thanks!

Thoma

-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-08-06 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 18:15 [Buildroot] [PATCH] imagemagick depends on pango even if not available Mauro Condarelli
2015-08-06 20:48 ` Thomas Petazzoni [this message]
2015-08-06 21:49   ` Mauro Condarelli
2015-08-06 22:01     ` Thomas Petazzoni
2015-08-06 22:04     ` Thomas Petazzoni
2015-08-10 14:16       ` Thomas Petazzoni

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=20150806224829.61effbfa@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