I know... I miss unix for this, anyway if I uncheck every modularizing
project for the building ("<something>-modularize") the headers of
<something> are not erased. This seems work, but the problem is that
every time that you rebuild, cmake's generation is launched again and so
while a rebuilding is performed, Visual C++ goes crazy because every
project file is changed under its nose. And all the
"<something>-modularize" projects are restored again in their default
configuration...I guess that this new cmake system in Windows is too much experimental... -----Original Message----- From: boost-cmake-boun...@lists.boost.org [mailto:boost-cmake-boun...@lists.boost.org] On Behalf Of troy d. straszheim Sent: woensdag 4 maart 2009 14:27 To: Discussion of the CMake-based build system for Boost Subject: Re: [Boost-cmake] Headers erased after the first building in VC8 of boost 1.38 Trimoldi, F. (Filippo) wrote: > Yes, in fact in the default configuration of my solution, both "INSTALL" > and "modularize" projects aren't checked for their building, but a the > end of my first building all my headers are erased... what I'm making a > mistake in? > I don't know. Unfortunately, I don't have any microsoft stuff here to verify. I'll guess that either there is a magic box checked someplace (I don't have any microsoft stuff in front of me right now), or the default target on windows isn't the same as it is on unix. -t _______________________________________________ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html _______________________________________________ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
