From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: Conditionally build documentation
Date: Fri, 14 Jan 2022 22:04:58 -0700 [thread overview]
Message-ID: <69605334-cded-ed59-4d8b-0477cdaf5b40@SystematicSw.ab.ca> (raw)
In-Reply-To: <DM8PR09MB70950BB104F774E1F959F7BEA5549@DM8PR09MB7095.namprd09.prod.outlook.com>
On 2022-01-14 13:18, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>> Add a configure option '--disable-doc' to disable building of the
>> documentation by the 'all' target.
> Can you please also add --disable-doc to "configure --help"? It took me awhile to figure out which option I should use to skip the doc from building because it does no longer ignore doc build failure by default (unlike it used to do). Also this fact is not reflected in the FAQ here:
>
> https://cygwin.com/faq.html#faq.programming.building-cygwin
>
> which still mentions the doc build errors ignored:
>> Normally, building ignores any errors in building the documentation
Updated by Jon a month ago:
https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=f4a26ececa180cec70c41b6dd2082ff730f92065
winsup/configure.ac:
...
+AC_ARG_ENABLE(doc,
+ [AS_HELP_STRING([--enable-doc], [Build documentation])],,
+ enable_doc=yes)
+AM_CONDITIONAL(BUILD_DOC, [test $enable_doc != "no"])
...
winsup/faq-programming.xml:
...
+Building the documentation also requires the <literal>dblatex</literal>,
+<literal>docbook2X</literal>, <literal>docbook-xml45</literal>,
+<literal>docbook-xsl</literal>, and <literal>xmlto</literal> packages.
Building
+the documentation can be disabled with the <literal>--disable-doc</literal>
+option to <literal>configure</literal>.
...
probably won't appear on the web site until the next release.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-01-15 5:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 20:18 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-15 5:04 ` Brian Inglis [this message]
2022-01-15 15:06 ` Jon Turney
2022-01-15 19:06 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-15 23:00 ` Brian Inglis
2022-01-18 20:01 ` Jon Turney
2022-01-17 19:39 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-18 19:57 ` Jon Turney
-- strict thread matches above, loose matches on Subject: below --
2021-12-18 17:47 Jon Turney
2021-12-20 9:55 ` Corinna Vinschen
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=69605334-cded-ed59-4d8b-0477cdaf5b40@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-patches@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).