Subject: Re: [boost] [modular-boost] Development procedures
From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2014-02-03 20:08:58
Daniel James <dnljms <at> gmail.com> writes:
> Boost build searches for includes when compiling C++ files in order to
> check if any have been updated, I believe it checks if the original
> file has been updated when doing that in order to update the link.
Hmmm.. I do not think I like this approach. What if I am not using
Boost.Build (I have VS projects for Boost.Test for example)? What if I just
want to see/grep the content of the file.
Any chance we can reconsider? This look like a very bad setup to me.
In my opinion this should be separate manual step or something which is done
when one is updating boost tree.
Interestingly, if we switch to links to directories, we do not need to do
anything in majority of the cases. Only when new library is added or old is
removed we need to chansge boost/ content.
> >> 'git submodule update' takes a long time as a fresh tree because it
> >> has to clone over a 100 modules.
> > I was running on freshly cloned tree. What else does it needs to clone?
> All the libraries and tools. If you have a clone of every module and
> it's still slow, then I have no idea. You haven't really explained
> what you've done and it's not that slow for me.
I followed the procedures on a wiki. I cloned *full* boost.org tree and run
"git submodule update" command on it.
> > What if I have local changes, but want to update to HEAD on master
> > branch of other libs? I think this is very common need and we should
> > document steps one needs to take for this.
> You could create a wiki page.
> > Can we setup some kind of scripts to help developers with routine tasks
> > like this?
> Yes you can.
I was not suggesting that you should be doing this. I was merely suggesting
that we *need* to do this.
Do we have anyone working on modular boost migration actively? Unfortunately
I am not in a position to volontier at the moment, but I think this is
important area and we need someone to be responcible for it.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk