Re: [Boost-cmake] [boost] trunk vs release (qtsync implementation)

2009-05-28 Thread troy d. straszheim
Ilya Sokolov wrote: troy d. straszheim wrote: 1. if you add or remove headers you'd have to rerun this script. 2. there's an extra #include hop in every error/warning. We could probably do something with links on unix to get around this. 3. it requires python It should be possible (in bbv

Re: [Boost-cmake] [boost] trunk vs release (qtsync implementation)

2009-05-28 Thread Juergen Hunold
Hi ! On Wednesday 27 May 2009 12:13:38 Ilya Sokolov wrote: > >troy d. straszheim wrote: > > 3. it requires python > > It should be possible (in bbv2, at least) to add a build system target > to overcome these limitations, isn't it? Most probably. file generation is done now (think response files)

Re: [Boost-cmake] trunk vs release (qtsync implementation)

2009-05-28 Thread Ilya Sokolov
troy d. straszheim wrote: 1. if you add or remove headers you'd have to rerun this script. 2. there's an extra #include hop in every error/warning. We could probably do something with links on unix to get around this. 3. it requires python It should be possible (in bbv2, at least) to add a