From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] imagemagick: disable documentation
Date: Mon, 17 Feb 2014 23:15:50 +0100 [thread overview]
Message-ID: <53028A16.40408@openwide.fr> (raw)
In-Reply-To: <53027DDA.6060102@mind.be>
Hi Arnout,
Le 17/02/2014 22:23, Arnout Vandecappelle a ?crit :
> 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?
It is not really needed, but all documentation is installed in staging
and target,
which hides compilation issues because logs are not long enough in
autobuilder.
http://autobuild.buildroot.net/results/612/612f2b258114cbb2c60359f19a9797c5ce8852ae/build-end.log
Then documentation is removed from target.
> 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.
Yes, but in the case of Imagemagick all html stuff is not generated,
it is just directly installed from the source directory.
Ok, this is probably not the best method to do this...
Best regards,
Romain Naour
next prev parent reply other threads:[~2014-02-17 22:15 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 ` [Buildroot] [PATCH 1/2] imagemagick: disable documentation Arnout Vandecappelle
2014-02-17 22:15 ` Romain Naour [this message]
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=53028A16.40408@openwide.fr \
--to=romain.naour@openwide.fr \
--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