"William E. Kempf" <wekempf@cox.net> wrote in message news:20030108174453.YIAW22825.lakemtao04.cox.net@smtp.east.cox.net...
That is not what he (or I) means. He is suggesting that the path to "shared_ptr.hpp" should be "$INCLUDE/boost/shared_ptr.hpp" rather than "$INCLUDE/boost/boost/shared_ptr.hpp", which is the way it is now. Everything would still be the same for including headers except that only a single search path is necessary to setup with the compiler.
That's the way it is now *only* if you set your include directories incorrectly. When they are properly set to $BOOST_ROOT then it's only <boost/shared_ptr.hpp>, not <boost/boost/shared_ptr.hpp>.
...which is precisely the point. You have to have a separate include directory for Boost, rather than a single directory which contains various libraries. I.e. it would be nice to have a directory structure like this: $INCLUDE/ Loki/*.* Boost/*.* And then have only a single header directory: $INCLUDE. I'm not talking about the paths in the source code (i.e. <boost/shared_ptr.hpp>); I'm talking about the include directories that the compiler searches, which is external to the source code. Paul Mensonides