"Victor A. Wagner Jr." <vawjr@rudbek.com> writes:
before firing up bjam. Of course, it will probably be in some other subdirectory of C:\Windows\WinSxS on your machine.
I added C:\WINDOWS\WinSxS\x86_Microsoft.VC80.DebugCRT_1fc8b3b9a1e18e3b_8.0.50215.4652_x-ww_a12cf373 to my system path (so all users would access it) and it apparently made no difference in my tests yes, I looked fro the file and pasted the directory name in rather than using the one that worked on your machine, apparently it's in the same place on mine.
The problem should be solved now, after going around and around with Martyn Lovell, Microsoft's libraries lead, for a couple of days (thanks, Martyn!) A new build step is required when creating DLLs from the command-line, having something to do with "manifests." You can read all about it here: http://msdn2.microsoft.com/library/bxf4ee9f(en-us,vs.80).aspx I have integrated the neccessary steps into BBv1, and will try to do the same with BBv2 ASAP. -- Dave Abrahams Boost Consulting www.boost-consulting.com