Final Getting Started Guide
I refactored the getting started guide into separate documents. Please see http://www.boost-consulting.com/boost/more/getting_started.html Library authors have not posted any working URLS of library-specific build instructions, so library names other than Boost.Python all link to the librarys' top-level pages. Enjoy -- Dave Abrahams Boost Consulting www.boost-consulting.com
On Fri, 2006-12-22 at 10:08 -0500, David Abrahams wrote:
I refactored the getting started guide into separate documents. Please see
http://www.boost-consulting.com/boost/more/getting_started.html
This looks great, Dave. Thanks for all your hard work on this! Cheers, Doug
David Abrahams wrote:
I refactored the getting started guide into separate documents.
Finally get around to really reading this... Looks good so far. Found one strange text. In <http://www.boost-consulting.com/boost/more/getting_started/windows.html#library-naming> there's a bit of text near the end that reads as: ...names always end in .a``— ``.lib indicates a static... Those (``) marks look out of place. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
The "Boost.Build reference manual" link in <http://www.boost-consulting.com/boost/more/getting_started/windows.html#conclusion-and-further-resources> doesn't point to where it should, probably due to the individual pages being in a subdir. ** Both the above and my previous post also apply to the unix instructions. ** -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Rene Rivera <grafikrobot@gmail.com> writes:
The "Boost.Build reference manual" link in <http://www.boost-consulting.com/boost/more/getting_started/windows.html#conclusion-and-further-resources> doesn't point to where it should, probably due to the individual pages being in a subdir.
** Both the above and my previous post also apply to the unix instructions. **
And "Michael Fawcett" <michael.fawcett@gmail.com> writes:
On 12/22/06, David Abrahams <dave@boost-consulting.com> wrote:
I refactored the getting started guide into separate documents.
Minor typo in the Windows footnotes section.
[7] ... All though it's true ...
Should be "Although".
Got it; thank you both. -- Dave Abrahams Boost Consulting www.boost-consulting.com
Rene Rivera <grafikrobot@gmail.com> writes:
David Abrahams wrote:
I refactored the getting started guide into separate documents.
Finally get around to really reading this... Looks good so far. Found one strange text. In <http://www.boost-consulting.com/boost/more/getting_started/windows.html#library-naming> there's a bit of text near the end that reads as:
...names always end in .a``— ``.lib indicates a static...
Those (``) marks look out of place.
Thanks, fixed. It'll show up on the site in a half hour or so. -- Dave Abrahams Boost Consulting www.boost-consulting.com
David Abrahams wrote:
I refactored the getting started guide into separate documents. Please see
http://www.boost-consulting.com/boost/more/getting_started.html
Library authors have not posted any working URLS of library-specific build instructions, so library names other than Boost.Python all link to the librarys' top-level pages.
For the thread lib this is: boost_root/doc/html/thread/build.html#thread.build.building This link is available after the docs have been built. No stub available. While trying to update this piece of the doc I found the following: 1) The getting started guide uses " --toolset= " while the bbv2 manual states " toolset= ". Obviously both versions work. Which one should go into the documentation? 2) The Boost.Build ref link from the windows.html getting started points to tools/build/v2. This might be fine when viewed over a web server but opens a directory when viewed from the filesystem. I suggest correcting this link to use the index.html file. 3) The only place I have found where toolset names are explicitely named is in the getting started guide. I intend to link to /more/getting_started/windows.html#identify-your-toolset. Questions are if this is a stable link and how this will work in a pdf scenario? 4) I tried to build the getting_started doc on my local machine. But no luck. What do I need beyond using docutils ; in my user-config.jam? Regards Roland
participants (5)
-
David Abrahams -
Douglas Gregor -
Michael Fawcett -
Rene Rivera -
Roland Schwarz