Re: [boost] Re: 1.32 documentation issue
----- Mensaje original ----- De: David Abrahams <dave@boost-consulting.com> Fecha: Miércoles, Noviembre 3, 2004 6:49 pm Asunto: [boost] Re: 1.32 documentation issue
"Robert Ramey" <ramey@rrsd.com> writes:
When using boost libraries, It is my custom to peruse the local copy of boost documentation on my hard drive. This avoids necessity to be connected to www.boost.org all the time which can be inconvenient in lots of cases.
The following scenario takes me a way from my local copy.
a) C:\boost_RC_1_32_0\index.htm b) select libraries c) select function programming section d) select function e) At this point I am automatically redirected to www.boost.org
I think I should be redirected to ./function.html instead.
It goes to the web intentionally, on the idea that developers who don't want to build the documentation (which involves installing an extensive toolchain) should be able to get to the Boost.Function documentation.
Isn't this contradictory with this reply? http://lists.boost.org/MailArchives/boost/msg74101.php I thought BoostBook-generated docs come prebuilt into the release tarball, at least for HTML. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
JOAQUIN LOPEZ MU?Z <joaquin@tid.es> writes:
----- Mensaje original ----- De: David Abrahams <dave@boost-consulting.com> Fecha: Miércoles, Noviembre 3, 2004 6:49 pm Asunto: [boost] Re: 1.32 documentation issue
"Robert Ramey" <ramey@rrsd.com> writes:
When using boost libraries, It is my custom to peruse the local copy of boost documentation on my hard drive. This avoids necessity to be connected to www.boost.org all the time which can be inconvenient in lots of cases.
The following scenario takes me a way from my local copy.
a) C:\boost_RC_1_32_0\index.htm b) select libraries c) select function programming section d) select function e) At this point I am automatically redirected to www.boost.org
I think I should be redirected to ./function.html instead.
It goes to the web intentionally, on the idea that developers who don't want to build the documentation (which involves installing an extensive toolchain) should be able to get to the Boost.Function documentation.
Isn't this contradictory with this reply?
http://lists.boost.org/MailArchives/boost/msg74101.php
I thought BoostBook-generated docs come prebuilt into the release tarball, at least for HTML.
Sorry, they do. I was referring to the CVS state. The release tarball should point at local docs. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
participants (2)
-
David Abrahams -
JOAQUIN LOPEZ MU?Z