public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: kawa <kawa@sourceware.org>
Subject: (minor) Installing docs built from source
Date: Sun, 07 May 2017 12:47:00 -0000	[thread overview]
Message-ID: <23049.1494161221@vereq.eip10.org> (raw)

This items mentioned below are all minor (and a bit nebulous/rambling),
related to installing (not building) the documentation.  It is also
possible that I'm the wrong make targets.

Building the documentation (epub, pdf, and two HTML varieties) works
fine with the current gitlab sources (on invoke branch).  However,
installing the documentation (using some combination of make
install-html etc. as suggested by the Makefile targets) doesn't work
properly.

Based on a quick look at doc/Makefile, it seems that the variable
KAWA_HTML_PARTS which is used by the install-html target is not defined.

I'm guessing that variable should be set to the web and/or kawa-html
subdirectories of doc where the 'fancy' and 'plain' HTML docs get built,
but perhaps there is more to it.

In particular, there is also the Javadoc HTML API documentation produced
by 'make install-html' in the main Kawa directory. (I discovered this
quite accidentally.)  Perhaps those should be included in
KAWA_HTML_PARTS too?  These API docs get built in $HOME/Kawa but perhaps
they should be built under Kawa/doc in the source directory (and then
optionally installed elsewhere) instead.  Perhaps it would also be
useful to add a note about building the API docs to the "installing from
source" section of the manual.  They may not be of interest to many
users, but users building from source may like to have them.  (I find
them nice to have for reference.)

It may also be useful to allow the HTML docs to be installed somewhere
relative to the value of the --prefix configure option instead of under
$HOME/public_html.

All the rest (make; make check; make install, etc.) works very smoothly
with the current version in gitlab.  (Testing on Debian 8/Jessie.)

Regards,

-chaw

                 reply	other threads:[~2017-05-07 12:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=23049.1494161221@vereq.eip10.org \
    --to=chaw@eip10.org \
    --cc=kawa@sourceware.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.
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).