From: Per Bothner <per@bothner.com>
To: kawa@sourceware.org
Subject: Re: make kawa-manual.epub (Re: please checkout Kawa from gitlab.com)
Date: Wed, 23 Nov 2016 18:05:00 -0000 [thread overview]
Message-ID: <7d3e7f20-008d-14f2-3711-852bed4001d4@bothner.com> (raw)
In-Reply-To: <4296.1479907059@vereq.eip10.org>
On 11/23/2016 05:17 AM, Sudarshan S Chawathe wrote:
> A quick report: I was able to build kawa-manual.epub as suggested below
> after creating a symlink to the system docbook-xsl directory as
> suggested in the Makefile. (The main Kawa build was fine too.)
Good - I was afraid there might be too many dependencies on my
personal setup.
I should add a --with-docbook-stylesheets=PATH configure
option, and have 'make all' default to building kawa-manual.epub
when this configure option is specified.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2016-11-23 18:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 0:59 proposal: move Kawa from Subversion to git on gitlab.com Per Bothner
2016-11-13 4:42 ` Jamison Hope
2016-11-13 5:06 ` Per Bothner
2016-11-16 0:53 ` invoke branch (was: proposal: move Kawa from Subversion to git on gitlab.com) Per Bothner
2016-11-13 17:51 ` proposal: move Kawa from Subversion to git on gitlab.com David Pirotte
2016-11-13 22:55 ` Charlie Turner
2016-11-13 23:37 ` Per Bothner
2016-11-22 16:57 ` please checkout Kawa from gitlab.com Per Bothner
2016-11-22 22:12 ` David Pirotte
2016-11-23 7:42 ` Per Bothner
2016-11-23 13:17 ` make kawa-manual.epub (Re: please checkout Kawa from gitlab.com) Sudarshan S Chawathe
2016-11-23 18:05 ` Per Bothner [this message]
2016-11-27 6:07 ` Per Bothner
2016-11-25 1:33 ` please checkout Kawa from gitlab.com Kumar Appaiah
2016-11-25 5:33 ` Per Bothner
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=7d3e7f20-008d-14f2-3711-852bed4001d4@bothner.com \
--to=per@bothner.com \
--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).