Subject: Re: [Boost-build] Doxygen rule change ?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-04-26 17:02:28
On 04/26/2016 12:40 PM, Edward Diener wrote:
> Most of the time it does appear to preserve the input order but when it
> does not do so I have little idea why that happens. I am guessing it has
> something to do with input files in different directories. Of course it
> is unreasonable to expect a library developer to change the placement of
> his files just to accomodate doxygen.
> I agree that most of the time changing xml should be done with xsl. But
> perhaps when it comes to moving around the different file information in
> the xml, since the file information is probably top-level in the
> hierarchy, it wouldn't just be easier reading in the entire xml and then
> writing it back out in a corrected order.
doxygen2boostbook.xsl is already part of
the toolchain. <xsl:sort> should do the
> I don't know what you mean when you say that Boost Build sorts things
> alphabetically. It seems to me that the the doxygen generated reference,
> which shows in the HTML documentation for a library using the
> quickbook-doxygen-boostbook toolsets, always show the files in the order
> in which doxygen generates the files information and writes the output
> to xml. They are definitely not transformed into any sort of
> alphabetical order as far as the actual file paths are concerned. Try
> creating the VMD doc and you will see that.
Okay. All I was saying was that /if/ Boost.Build
changed the order, /then/ it would only do so by
sorting the files. You implied that the results
are /not/ sorted. Therefore, Boost.Build is not
not the cause of the ordering problem.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk