|
[openbeos]
||
[Date Prev]
[09-2006 Date Index]
[Date Next]
||
[Thread Prev]
[09-2006 Thread Index]
[Thread Next]
[openbeos] Documentation tools in the source tree
- From: "Niels Reedijk" <niels.reedijk@xxxxxxxxx>
- To: "Haiku Mailinglist" <openbeos@xxxxxxxxxxxxx>
- Date: Fri, 1 Sep 2006 12:01:42 +0000
Hi,
Since there was a consensus on docbook, I thought it would be nice to
have the docbook tools integrated into the tree to lower the barrier
of entry for everyone that wants to contribute on some sort of doc.
The following changes are in my local tree:
- trunk/src/libs/libxml2 -- contains libxml2 version 2.6.26
- trunk/src/libs/libxslt -- contains libxslt version 1.1.16
- trunk/headers/libs/libxml2 -- contains the headers of libxml2 as
needed by libxslt
- trunk/src/documentation/docbook-dtd -- contains the docbook dtd version 4.2
- trunk/src/documentation/docbook-xsl -- contains the docbook xslt
sheets version 1.70.0
I also changed the documentation rules. What happens is this: if you
want to build the documentation, jam will construct the target
<build>xsltproc, which depends on <build>libxslt.a, which depends on
<build>libxml2.a. This tool will, with the help of the dtd and xsl
sheet, generate the actual documentation.
I've got the Jam magic almost working, the only issue I have is
setting the XML_CATALOG_FILES shell variable in the Doc2Html1 rule in
the file DocumentationRules. I doubt that I've got the magic right
though :-) Ingo, if you'd be able to help out a bit if this change is
accepted, I'd be grateful.
So, what I'm writing for are these points.
* Is the idea to integrate the doc tools into the tree accepted?
* Is my implementation of the integration okay?
* If yes, how do I effectively integrate it into svn, taking into
account the existence of vendor branches and stuff?
Any thoughts?
Niels
|