|
Boost : |
From: John Maddock (john_at_[hidden])
Date: 2007-05-17 13:28:14
Bjørn Roald wrote:
>
> Well -namespace=boost_1_34_0 actually does a bit more. It renames
> directories and include directives so stuff like
>
> #include <boost/filesystem/path.hpp>
>
> becomes
>
> #include <boost_1_34_0/filesystem/path.hpp>
>
> and should work. It also replaces all instances of BOOST_ prefix in
> preprocessor symbol definitions and references with BOOST_1_34_0_ and
> processes Jamfiles as well so my hope was that all should build, test,
> and work without touch up work.
>
> Also in the general case
>
> ../bin/boost/libs/filesystem/build/libboost_filesystem.a/gcc/debug/libboost_filesystem-gcc-d-1_33_1.a
>
> should become
>
> ../bin/boost_1_34_0/libs/filesystem/build/lib/boost_1_34_0_filesystem.a/gcc/debug/libboost_1_34_0_filesystem-gcc-d-1_33_1.a
>
> In this specific case the additional 1_34_0 substrings are just
> annoyance, so I guess we need to treat it as a special case when we
> have
> a version part of the new namespace. But as I said library path
> naming
> is not implemented yet. I guess this can be done by treating some
> configuration files for the build system. This may be outside the
> scope
> of the bcp tool.
>
> So.. given all this, are you still sure this is worth adding?
Sure, why not.
> Also, is -namespace the best name for the command line option?
Yep.
> I have working code and will happily merge with 1.34.0 version of bcp
> and provide you a patch. Then you can use what you like, fix what
> you
> like to fix, and dump what you don't like :-)
OK :-)
Cheers, John.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk