Boost logo

Boost-Build :

Subject: Re: [Boost-build] Documentation build error on trunk
From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2012-08-14 09:36:22


   Hi.

> I fixed some some syntax errors, added a missing import and fixed the
> name of BoostBook (it isn't called Boost.Book, it's following
> DocBook).

   Great! Thanks!

   As for the 'Boost.Book' naming - that was inherited from the original
code base. :-)

> I haven't done an actual build yet.
>
> Running 'b2 -n' I got lot of odd errors. I don't think they're related
> to doxygen. They might not even be new as they don't make the build
> fail. I'll look into it this evening. Here's a few of them:
>
> don't know how to make
> <p../bin.v2/libs/asio/doc/darwin-4.2/debug-object(xinclude-scanner)@6604>asio_doc.xml
> don't know how to make

   Unfortunately, I do not really know where these come from. I tried
running the build from the trunk using msvc (i.e. no documentation
build) and I get no such messages with or without the '-n' option.

   You can try running the same build on the last release archive but
using the --boost-build=... option to use Boost Build from the trunk.

   You can also try running the same '-n' command directly on the last
release archive using Boost Build from there to see whether these
messages were present there also.

   Hmm, just a thought - they could possibly be related to targets that
need to be generated first for some other targets to 'start making
sense', and since you are running the build with the '-n' option - the
original targets do not get built, causing Boost Build to 'not know how
to build' the targets in the second group. If this is so then they
should not appear in a regualr build.

   Hope this helps.

   Best regards,
     Jurko Gospodnetić


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