Re: Failure to Build quickbook docs when indexing isenabled
John Maddock <[email protected]>
| Newsgroups | gmane.comp.lib.boost.documentation |
|---|---|
| Message-ID | <952B6B5C191540B7A6B1578BACCA540C@acerlaptop> |
> It builds OK without --enable-index in the bjam command. > > The error reported is > > xslt-xsltproc.windows > bin\msvc-10.0\debug\auto-index-internal-on\auto-index-verbose-on\auto-index-on\threading-multi\autod > oc-xml.doxygen > file:///I%3A/boost-sandbox/endian_2/libs/endian/doc/bin/msvc-10.0/debug/auto-index-internal-on/auto- > index-verbose-on/auto-index-on/threading-multi/autodoc-xml/index.xml:150: > parser error : Opening and > ending tag mismatch: compound line 24 and doxygenindex > > ... > </doxygenindex> > > John has pointed out that this can't be the autoindex program itself > because this isn't run yet. > > I've tried deleting the /bin folder (and repeating with bjam -a (with the > same results)) > > but this gives a possible clue > > "The folder contains items whose names are too long for the recycle > bin" > > The Doxygen log also contains the following warnings about files not being > available for writing > > Cannot open file > I:/boost-sandbox/endian_2/libs/endian/doc/bin/msvc-10.0/debug/auto-index-internal-on/auto-index-verb > ose-on/auto-index-on/threading-multi/autodoc-xml/classboost_1_1endian_1_1endian_3_01endianness_1_1li > ttle_00_01_t_00_01n__bits_00_01alignment_1_1aligned_01_4.xml for writing! > Cannot open file > I:/boost-sandbox/endian_2/libs/endian/doc/bin/msvc-10.0/debug/auto-index-internal-on/auto-index-verb > ose-on/auto-index-on/threading-multi/autodoc-xml/classboost_1_1endian_1_1endian_3_01endianness_1_1li > ttle_00_01_t_00_01n__bits_00_01alignment_1_1unaligned_01_4.xml for > writing! > Cannot open file > I:/boost-sandbox/endian_2/libs/endian/doc/bin/msvc-10.0/debug/auto-index-internal-on/auto-index-verb > ose-on/auto-index-on/threading-multi/autodoc-xml/classboost_1_1endian_1_1endian_3_01endianness_1_1na > tive_00_01_t_00_01n__bits_00_01alignment_1_1unaligned_01_4.xml for > writing! > > This looks as though a limit on the filename length might be > reached/exceeded? There's an (undocumented?!?) --hash option to boost build which fixes that issue - of course the directory names become unreadable in that case... HTH, John.