"Brian Braatz" <brianb@rmtg.com> writes:
My plan (to address this organically): * First off finish my other work :) * then spend the time to really get my head wrapped around bjam\boost build * debug my own build problems- and make careful notes on "what the problems were" * Post-Mortem- build a tool that WOULD have shown me the problem immediately. I.e. (weak example:) if my bjam.exe is the wrong version- then the tool would simply report the version
Again, shouldn't bjam itself just do this? It would be easy for Boost.Build to know what version of bjam it requires and complain if bjam is not up-to-date.
* share the tool with the rest of the community. * watch the users list for folks having build problems- offer to help them- use the tool as a proxy for figuring out their problems- in this way the tool evolves the ability to solve the common problems. OR it becomes clearly proven that this is not possible. (my gut tells me it IS possible) * I am going to save this mail off, and then when I have learned a few things by doing above, I may "re-open" this thread with what I have learned.
Thank you David for a very useful conversation. :)
Sure thing. I hope it leads to useful tools! -- Dave Abrahams Boost Consulting www.boost-consulting.com