As I mentioned on the devel mailing list a few days ago, I'm trying to finish converting the Boost.Thread documentation to BoostBook format (Bill Kempf started doing this on the thread_dev branch in cvs, but never quite finished).
After getting past a couple of initial hurdles in getting BoostBook to run on my machine, I simply added the appropriate library section to boost.xml, like this:
<xi:include href="../../libs/thread/doc/thread.xml"/>
and everything worked great!
Now for the question. The file thread.xml also has <xi:include/> entries in it. If I edit one of those included files and run BoostBook, nothing rebuilds; however, if I modify thread.xml and run BoostBook, then it does rebuild. Any idea why it's not noticing the changes one level deeper? Should it?
I assume this is because thread.xml is referenced in a BB project file and bjam will check if it has been modified and rebuild appropriately. The other files will not have a BB entry as they do not require being built seperately (BB will allow you to rebuild just the thread docs).
BB does not search the XML file for xi:included files, like it does not check source code for header files. But in a makefile, you can list dependant targets like:
hello.cpp : myinclude1.hpp anotherincl.h
Therefore, the question becomes: is there a similar mechanism in BB/bjam?
Regards, Reece
_________________________________________________________________
Use MSN Messenger to send music and pics to your friends http://www.msn.co.uk/messenger
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
