Re: [boost] [Git] Documentation for Git and Modular Boost conversion

Subject: Re: [boost] [Git] Documentation for Git and Modular Boost conversion
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2012-12-14 12:25:46

> -----Original Message-----
> From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]] On Behalf Of Daniel
Pfeifer
> Sent: Friday, December 14, 2012 5:05 PM
> To: boost_at_[hidden]
> Subject: Re: [boost] [Git] Documentation for Git and Modular Boost conversion
> 
> 2012/12/14 Paul A. Bristow <pbristow_at_[hidden]>
> 
> >
> > > -----Original Message-----
> > > From: boost-bounces_at_[hidden] [mailto:
> > boost-bounces_at_[hidden]] On Behalf Of Beman
> > > Dawes
> > > Sent: Saturday, December 08, 2012 4:03 PM
> > > To: boost_at_[hidden]
> > > Subject: Re: [boost] [Git] Documentation for Git and Modular Boost
> > conversion
> > >
> > > On Fri, Dec 7, 2012 at 3:42 PM, Eric Niebler <eric_at_[hidden]> wrote:
> > > > On 12/7/2012 11:44 AM, Oliver Kowalke wrote:
> > >
> > > >> Do I have to clone an additional submodule (which is not
> > > >> mentioned in the docu)?
> > > >
> > > > Beman's docs appear to lack instructions for how to clone the
> > > > super-project and initialize the sub-modules. That would be a nice
> > > > addition. I don't know the steps and can't find them ATM, but I
> > > > know it's documented *somewhere*. Beman?
> > >
> > > Just added: https://svn.boost.org/trac/boost/wiki/TryModBoost
> >
> > I've tried to carry out these instructions but changing the names and
> > files a tiny bit (Windows 7)
> >
> >  but I've stumbled at the test run stage with
> >
> > thrice_test.cpp
> > thrice_test.cpp(1) : fatal error C1083: Cannot open include file:
> > 'boost/trivial/twice.hpp': No such
> >  file or directory
> >
> > but it is here
> >
> > I:\boost-trunk\libs\trivial\include\boost\trivial\thrice.hpp
> >
> 
> thrice != twice! Is that a typo in your email or in your code?

No I wanted to change the name of the library and its code.  Does "boobooboo" ;-)
 
> > I *think* I've got the directory structure right, and I created a
> > symbolic link that looks
> > promising:
> >
> > I:\boost-trunk\boost>mklink /d trivial
> > ..\libs\trivial\include\boost\trivial
> >
> 
> So you tried to create the symlinks manually...

https://svn.boost.org/trac/boost/wiki/StartModDev
  says
"Create a symlink to simulate your library being installed as part of Boost:

    Windows: mklink /d simple ..\libs\simple\include\boost\simple
    POSIX: ln -s ../libs/simple/include/boost/simple simple"

> If you followed the documentation, you should have called this instead:
> 
> cmake -P forward_headers.cmake

Huh?  I'm not using cmake am I?  I'm using bjam/b2 aren't I?

But thanks

Paul