Compiling Manual: Difference between revisions
New page: === How to Compile the Manual for Bluefish from CVS source The source for the bluefish manual is in the bluefish-doc directory of bluefish, but the manual for is not produced during the c... |
mNo edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
== How to Compile the Manual for Bluefish from CVS source== | |||
The source for the bluefish manual is in the bluefish-doc directory of bluefish, | The source for the bluefish manual is in the bluefish-doc directory of bluefish, |
Latest revision as of 10:43, 27 October 2008
How to Compile the Manual for Bluefish from CVS source
The source for the bluefish manual is in the bluefish-doc directory of bluefish, but the manual for is not produced during the compiling of bluefish. It must be compiled separately.
In order to do this, you need to first download the source from the bluefish directory. The cvs is in the same directory at sourceforge.
cvs -d:pserver:anonymous@cvs.bluefish.sourceforge.net:/cvsroot/bluefish login
cvs -z3 -d:pserver:anonymous@cvs.bluefish.sourceforge.net:/cvsroot/bluefish checkout bluefish-doc
The two directories, bluefish-gtk2 and bluefish-doc should be in the same parent directory on your computer just as they are in the cvs.
The README in bluefish-doc tells you what you need to have to make it work. In part it says to download docbook-xsl-1.67.2.tar.gz (or later), then unpack it in the bluefish-doc directory. docbook-xsl can be found at http://sourceforge.net/projects/docbook/.
From the bluefish-doc directory, run 'make html' to produce a chunked version in html format.
See the README for details and other formats.