gast128
A significant number of questions posted here is about linking errors and thus prebuilt boost libraries.
Yes.
If I am new to a library, I should exactly told what to do (click on this, click on that),
Unfortunately, "click click" style instructions tend to be very specific to one group of people. In the case of Visual Studio users, it's a very large group, and maybe we should make special accomodations. I can certainly make some mention of this in my talk. However, you must realize that it's extra effort for anyone doing the documentation.
and therefore made an article on www.codetools.com 'Building Boost libraries for Visual Studio' intended for the same audience as myself.
Nice! But it looks wrong at step 1. The bjam commands you show there do not generate batch files as you claim. They build the Boost libraries!
In general I find the boost documentation not too bad, but as always it could better. Perhaps a good tip is to let a third person write the documentation,
Hehehe. Good tip. We'd be happy to allow a third person write the docs (if that person can do a good job) -- the problem is finding competent third persons who are willing to do it!
but this can be difficult since most people have regular jobs.
Further on, I still haven't figured out, how to print these new boost book format... A prebuilt pdf or big html would be nice here...
Interesting. Doesn't help much with my talk; maybe you should post this to the boost-docs mailing list, where someone who can do something about it will respond. -- Dave Abrahams Boost Consulting www.boost-consulting.com