|
From: | Anirudha Bose |
Subject: | Re: Installing Documentation |
Date: | Mon, 29 Jul 2013 16:26:39 +0530 |
On Sun, Jul 28, 2013 at 8:31 PM, Rik <address@hidden> wrote:
Anirudha,On 07/28/2013 12:30 PM, Anirudha Bose wrote:
On Sun, Jul 28, 2013 at 7:21 PM, Rik <address@hidden> wrote:
On 07/28/2013 05:30 AM, address@hidden wrote:
> On the installer aspect, one thing that is missing is the inclusion of
> octave documentation; If I'm not mistaken, the HTML and PDF version of
> octave are not present in the installer. Could you add them? I think those
> are not installed by the octave's Makefile, that's why they're not present
> in the installer. So you'll have to force their installation in the MXE's
> octave.mk. It would then be nice to add links in the start menu for the
> octave documentation
7/28/13
The documentation is built when --enable-docs is present, but it is still
not installed by default. To do so, use 'make install-<DOCTYPE>'. For
example, 'make install-pdf' or 'make install-html'.
Thanks Rik. Is it possible to build both the html as well as pdf version of documentation with a single make command? Otherwise I think it is enough if we just include the PDF docs.
All of the documentation is always built; It is only a question of which parts gets installed. By default, just the Info documentation is installed. If you have a script, can't it support two calls to make? If not, you could add a new rule to Makefile.am at the toplevel. Something like
install-alldoc: install-html install-pdf
and then you could make a single 'make install-alldoc' command in the script.I really don't get what's the problem here. Why isn't "make install-html install-pdf" suitable (note that it's a single command, just providing 2 targets to "make")?
Michael.
[Prev in Thread] | Current Thread | [Next in Thread] |