From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Makeinfo
Date: Wed, 20 Nov 2013 08:54:30 +0100 [thread overview]
Message-ID: <528C6AB6.1080609@mind.be> (raw)
In-Reply-To: <528B9B14.3080708@mind.be>
On 19/11/13 18:08, Arnout Vandecappelle wrote:
> On 19/11/13 11:45, Thomas De Schampheleire wrote:
[snip]
>> +#
>> +# Also, disable documentation by undefining makeinfo
>> STRESS_CONF_OPT = \
>> - $(if $(BR2_PREFER_STATIC_LIB),,--disable-static)
>> + $(if $(BR2_PREFER_STATIC_LIB),,--disable-static) \
>> + MAKEINFO=:
>>
>> $(eval $(autotools-package))
>> -------------
>>
>> I'm now wondering if this is an approach we could add globally: set
>> MAKEINFO to : to effectively disable the generation of
>> documentation...
>
> I still have the feeling it is a bit of a hack. But it's true, it could
> be part of DISABLE_DOCUMENTATION.
I found in gcc.mk how to make it less than a hack:
$(2)_CONF_OPT += MAKEINFO=missing
That should work for all real autotools environments, and is the way
that autoconf handles missing makeinfo to start with.
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
prev parent reply other threads:[~2013-11-20 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 10:45 [Buildroot] Makeinfo Thomas De Schampheleire
2013-11-19 17:08 ` Arnout Vandecappelle
2013-11-20 7:54 ` Arnout Vandecappelle [this message]
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=528C6AB6.1080609@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.