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 2/2] Compile Poppler over Qt
Date: Tue, 4 Mar 2014 15:44:46 +0100	[thread overview]
Message-ID: <20140304154446.42c57533@skate> (raw)
In-Reply-To: <1393940343-15899-1-git-send-email-jeremie.scheer@armadeus.com>

Dear jeremie.scheer at armadeus.com,

On Tue,  4 Mar 2014 14:39:03 +0100, jeremie.scheer at armadeus.com wrote:
> From: Jeremie Scheer <jeremie.scheer@armadeus.com>
> 
> 
> Signed-off-by: Jeremie Scheer <jeremie.scheer@armadeus.com>
> ---
>  package/poppler/poppler.mk |    9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/package/poppler/poppler.mk b/package/poppler/poppler.mk
> index 040327f..7dce7a0 100644
> --- a/package/poppler/poppler.mk
> +++ b/package/poppler/poppler.mk
> @@ -7,10 +7,17 @@
>  POPPLER_VERSION = 0.24.4
>  POPPLER_SOURCE = poppler-$(POPPLER_VERSION).tar.xz
>  POPPLER_SITE = http://poppler.freedesktop.org
> -POPPLER_DEPENDENCIES = fontconfig
>  POPPLER_LICENSE = GPLv2+
>  POPPLER_LICENSE_FILES = COPYING
>  POPPLER_CONF_OPT = --with-font-configuration=fontconfig
> +POPPLER_INSTALL_STAGING = YES
> +
> +ifeq ($(BR2_PACKAGE_QT),y)
> +	POPPLER_DEPENDENCIES = qt fontconfig
> +else
> +	POPPLER_DEPENDENCIES = fontconfig
> +	POPPLER_CONF_OPT += --disable-poppler-qt4

Why isn't the fontconfig dependency part of the if, and not kept
outside, since it is not related to Qt ?

Also, if poppler has a --disable-poppler-qt4 in one case, it probably
has a --enable-poppler-qt4 option in the other case, no?

Thanks!

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

  reply	other threads:[~2014-03-04 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 13:39 [Buildroot] [PATCH 2/2] Compile Poppler over Qt jeremie.scheer at armadeus.com
2014-03-04 14:44 ` Thomas Petazzoni [this message]
2014-03-26 10:35   ` Jeremie Scheer

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=20140304154446.42c57533@skate \
    --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