Subject: [Boost-build] process_jam_log & boost build
From: Robert Ramey (ramey_at_[hidden])
Date: 2012-10-30 16:57:45
I'm working on using the boost_build/process_jam_log/library_test
combination to build/test libraries outside of the boost tree. It seems I
can "almost" get there. The current status of this effort can be found at
www.blincubator.com -- simple tools / build_test - scroll to the end.
But in making tweaks to process_jam_log I'm wondering about the the
As I understand it, process_jam_log scrapes the bjam.log file and addes
test???.xml files to each leaf in the directory bin/test/...
My question is: Is there any reason that this wasn't or can't be just added
to the bjam scripting files themselves? That is if I use the bjam script
"target"? run - can't that just be altered to create the test???.xml file at
the same time it creates everything else? This would eliminate the somewhat
kludgy/hacky process_jam_log and seemingly make things a lot simpler.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk