|
Boost : |
From: pbristow_at_[hidden]
Date: 2021-03-05 10:35:15
> -----Original Message-----
> From: Boost <boost-bounces_at_[hidden]> On Behalf Of Andrey Semashev via Boost
> Sent: 4 March 2021 19:52
> To: boost_at_[hidden]
> Cc: Andrey Semashev <andrey.semashev_at_[hidden]>
> Subject: Re: [boost] [quickbook] Broken links generated in locally built docs
>
> On 3/4/21 8:18 PM, Paul A Bristow via Boost wrote:
> >>
> >> There are no "no ID for constraint linkend" errors in your output,
> >> though it still has errors from the commented line. Could you update libs/log and try again?
> >>
> >> Also, what is your DocBook XML version
> >
> > "C:/Program Files (x86)/DocbookXML/42" # dir exists and contains
> > docbookx.dtd 4.2
> >
> > Paul_at_hetpD MINGW64 /c/Program Files (x86)/xsltproc_win32 $
> > ./xsltproc.exe -V Using libxml 20630, libxslt 10122 and libexslt 813
> > xsltproc was compiled against libxml 20630, libxslt 10122 and libexslt
> > 813 libxslt 10122 was compiled against libxml 20630 libexslt 813 was
> > compiled against libxml 20630
> >
> >> and how are you running b2? I'm running: b2 -j8 release from libs/log/doc.
> >
> > $ b2 > log_doc_4mar2021_1705.log zip attached.
> >
> > So using all available cores (since you ask: 24 ð )
> >
> > Same result - much ambiguity.
> >
> > I have seen this before when things were declared twice.
>
> Don't mind the namespace warnings Doxygen throws. My understanding is that it has issues with
> multiple overloads of the same function, but eventually generates acceptable docs.
Yes this is my experience too - but I did some work to avoid the warnings to avoid clutter of warnings obscuring real warnings.
Boost.Inspect doesn't reveal anything amiss.
Inspection from path "html" including sub-folders.<br>
669 files scanned,<br>
51 directories scanned (including root),<br>
0 problems reported.
(After I had deleted the /html and rebuilt it ð )
Attached zip of /html
https://www.dropbox.com/s/zeguvc4bgyklac8/log_html.7z?dl=0
Looks nice enough to me ð
> I tried using DocBook DTD 4.2 and XSL 1.75.2, as specified in tools/boostbook/setup_boostbook.sh, but
> still no luck - the issue is the same. This is really strange.
I remember very faintly trying a more recent version of one of these two tools and the build didn't work so reverted on the thinking that "If it isn't broken, don't fix it."
Portability is wonderful ?
> > Still not helping much ... â¹
Paul
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk