All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] imagemagick: disable documentation
Date: Mon, 17 Feb 2014 22:23:38 +0100	[thread overview]
Message-ID: <53027DDA.6060102@mind.be> (raw)
In-Reply-To: <1392508668-27561-1-git-send-email-romain.naour@openwide.fr>

On 16/02/14 00:57, Romain Naour wrote:
> There is no options to disable the documentation,
> so remove it directly in Makefile.am
> 
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>

 Why is this needed?


 Side-track: perhaps we should add stubs for makeinfo, help2man,
asciidoc, xmlto, docbook2*, ... in $(HOST_DIR)/usr/bin, so we can disable
all documentation in one fell swoop.


 Regards,
 Arnout
-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2014-02-17 21:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15 23:57 [Buildroot] [PATCH 1/2] imagemagick: disable documentation Romain Naour
2014-02-15 23:57 ` [Buildroot] [PATCH 2/2] imagemagick: use --without-bzlib when bzip2 is not selected Romain Naour
2014-02-26  8:47   ` Peter Korsgaard
2014-02-17 21:23 ` Arnout Vandecappelle [this message]
2014-02-17 22:15   ` [Buildroot] [PATCH 1/2] imagemagick: disable documentation Romain Naour
2014-02-17 23:07     ` Arnout Vandecappelle
2014-03-01 23:22 ` Thomas Petazzoni
2014-03-02 10:45   ` Romain Naour

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=53027DDA.6060102@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.