Hi Peter,
Thanks for the info. I'm planning to contribute to serialization. Do the instructions you provided still work for this case, or do I need to adapt them?
Also, is there a way of forking boost completely, or should I just fork individual libraries?
Thanks,
Sean.
-----Original Message-----
From: Boost
Hi,
Once I have forked an individual boost library, what is the best way of building the library with b2? How are dependencies on other libraries handled?
Secondly, how can I build, run and debug tests using visual studio?
Which specific library do you have in mind?
The easiest way to run the tests is to just clone the whole Boost, with git clone --recursive, run `b2 headers`, then cd into libs/<library>/test and run b2 -j8 (or however many cores you have).
In general - unless the library contains a VS project - there's no good way to run the tests under Visual Studio (or if there is, I don't know it.) What I do is run the tests with b2, and if I need to debug one of them, I make a project that does #include