But that pushes the burden of dependency checking onto the developer, which essentially negates most of the value of having a build system. I want to know immediately if I make some change that has ripple effects on other libraries, e.g. I might have updated a header file, so that other libs need to be rebuilt to interface properly. In this case that /fast target would build something that was useless. There is nothing fundamental about the dependency checking that should take so long (I know this because I have an existing build system that does it much faster). It takes so long because cmake does this dependency checking by invoking make many MANY times.
Kevin 2010/7/26 Alexander Neundorf <a.neundorf-w...@gmx.net> > If you want to build just one target, e.g. "foo", there are targets > "foo/fast" > which skip the dependency skipping of dependent targets, i.e. it doesn't > check the dependencies of libraries against which foo links. > > So, most of the time is spent in dependency checking. > > Alex >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
