From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: [PATCH 1/8] configure: check for makeinfo and install-info
Date: Mon, 21 May 2018 13:08:49 -0700 [thread overview]
Message-ID: <20180521200856.17103-2-david@tethera.net> (raw)
In-Reply-To: <20180521200856.17103-1-david@tethera.net>
These are needed to build and install (respectively) the info format
documentation.
---
configure | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/configure b/configure
index cbb3b7cc..37db04d0 100755
--- a/configure
+++ b/configure
@@ -633,6 +633,8 @@ if [ $WITH_RUBY = "1" ] ; then
fi
have_sphinx=0
+have_makeinfo=0
+have_install_info=0
if [ $WITH_DOCS = "1" ] ; then
printf "Checking if sphinx is available and supports nroff output... "
if command -v sphinx-build > /dev/null && ${python} -m sphinx.writers.manpage > /dev/null 2>&1 ; then
@@ -641,6 +643,20 @@ if [ $WITH_DOCS = "1" ] ; then
else
printf "No (so will not install man pages).\n"
fi
+ printf "Checking if makeinfo is available... "
+ if command -v makeinfo > /dev/null; then
+ printf "Yes.\n"
+ have_makeinfo=1
+ else
+ printf "No (so will not build info pages).\n"
+ fi
+ printf "Checking if install-info is available... "
+ if command -v install-info > /dev/null; then
+ printf "Yes.\n"
+ have_install_info=1
+ else
+ printf "No (so will not install info pages).\n"
+ fi
fi
if [ $WITH_DESKTOP = "1" ]; then
@@ -1068,6 +1084,12 @@ HAVE_EMACS = ${have_emacs}
# Whether there's a sphinx-build binary available for building documentation
HAVE_SPHINX=${have_sphinx}
+# Whether there's a makeinfo binary available for building info format documentation
+HAVE_MAKEINFO=${have_makeinfo}
+
+# Whether there's an install-info binary available for installing info format documentation
+HAVE_INSTALL_INFO=${have_install_info}
+
# Whether there's a doxygen binary available for building api documentation
HAVE_DOXYGEN=${have_doxygen}
--
2.17.0
next prev parent reply other threads:[~2018-05-21 20:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 20:08 install info docs v1 David Bremner
2018-05-21 20:08 ` David Bremner [this message]
2018-05-26 15:56 ` [PATCH 1/8] configure: check for makeinfo and install-info David Bremner
2018-05-21 20:08 ` [PATCH 2/8] configure: set 'infodir' David Bremner
2018-05-21 20:08 ` [PATCH 3/8] doc: install build and install info pages David Bremner
2018-05-21 20:08 ` [PATCH 4/8] doc: install info files in elpa package David Bremner
2018-05-21 20:08 ` [PATCH 5/8] debian: install info pages as part of elpa-emacs David Bremner
2018-05-21 22:23 ` Tomi Ollila
2018-05-21 20:08 ` [PATCH 6/8] doc: initial documentation for notmuch-show-mode David Bremner
2018-05-21 20:08 ` [PATCH 7/8] doc: initial documentation for notmuch-tree mode David Bremner
2018-05-21 20:08 ` [PATCH 8/8] docs: add initial documentation for notmuch-tag-jump David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180521200856.17103-2-david@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).