id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
3240,Boostbook documentation is built under the current working directory.,Daniel James,Vladimir Prus,"For a demonstration, change to `$BOOST_ROOT`, and run:

    bjam libs/static_assert/doc/

The documentation is built in `$BOOST_ROOT/html` when I'd expect it to be built in `$BOOST_ROOT/libs/static_assert/doc/html`. The css file is installed to `$BOOST_ROOT/libs/static_assert/doc/html` so the links to it are broken. Also, for some other documentation, links are broken unless it's built in the correct location.

If this is fixed, the asio documentation build will have to be fixed as it relies on the current behaviour. In `doc/Jamfile.v2` an alias is used which builds the documentation in `doc/html`, so ideally there should be a way to preserve that - perhaps a parameter to specify the destination, in a similar manner to `install`.

This isn't a priority as it doesn't create any real problems in practice but it would be nice as it would make it easy to create a Jamfile which builds all the boostbook documentation, including 'standalone' documentation.",Bugs,new,To Be Determined,build,Boost 1.39.0,Problem,,,