I have just tried the tool. On the whole, it's very usefull. Thanks to John!
However, it seems to be confused by the preprocessor library. Since the
includes sometime have the form:
#include BOOST_PP_ITERATE()
the 'bcp' tool does not find them. For example,
"boost/preprocessor/iteration/detail/iter directory is needed by
boost/function.hpp but is not included. I've added some explicit dependencies
with the attached patch --- can it be applied?
Another note is on usability. Say I create directory "po" and find that some
files are missing. I tweak bcp source and try again. But attempt to override
files fail. I remove "po" directory. But then "bcp" says the destination does
not exist. It's a bit inconvenient --- maybe destination directory should be
created if it does not exist. Or maybe, there should be --overwrite switch,
which would simply clean up destination before doing copies.
And the last note:
bcp --boost=/home/ghost/Work/boost boost/function/function1.hpp function1
creates a tree of 1975 kbytes. Hmm, never though there's that many
dependencies...
- Volodya
Index: add_path.cpp
===================================================================
RCS file: /cvsroot/boost/boost/tools/bcp/add_path.cpp,v
retrieving revision 1.1
diff -u -r1.1 add_path.cpp
--- add_path.cpp 9 Jun 2003 11:52:33 -0000 1.1
+++ add_path.cpp 19 Jun 2003 10:53:57 -0000
@@ -137,6 +137,9 @@
std::pair<fs::path, fs::path>("tools/build/allyourbase.jam", "Jamrules"),
std::pair<fs::path, fs::path>("tools/build/allyourbase.jam", "project-root.jam"),
std::pair<fs::path, fs::path>("tools/build/allyourbase.jam", "boost-build.jam"),
+ std::pair<fs::path, fs::path>("boost/preprocessor/iterate.hpp",
+ "boost/preprocessor/iteration"),
+ std::pair<fs::path, fs::path>("boost/function.hpp", "boost/function/detail")
};
for(unsigned int n = 0; n < (sizeof(specials)/sizeof(specials[0])); ++n)
{
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
