I prefer keep it simply. 2012/9/24 Peter Kümmel <[email protected]>
> On 23.09.2012 15:04, Wouter van Kleunen wrote: > >> >> I had the following idea to speed up the building even more, if a tool >> can be build in ninja to list all files that need to be stat when >> building a project. These files can be monitored by qtcreator and later >> be provided as input again to ninja. So my idea works as follows: >> >> 1. Build project using cmake + ninja >> 2. Get file list of all dependencies by using ninja (something like >> ninja -t deplist). >> 3. Monitor the files using qt creator + qfilesystemwatcher >> >> When the user requests a rebuild: >> 4. Execute a ninja build command + provide the list of changed files. >> This way ninja won't have to stat any file. >> 5. Ninja builds >> >> Is this feasible ? >> > > I assume Qt Creator does it this way for qbs. > But for ninja this would be too much work. > > You think even ninja is too slow? > > > Peter > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/** > opensource/opensource.html<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<http://www.cmake.org/Wiki/CMake_FAQ> > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/**listinfo/cmake<http://www.cmake.org/mailman/listinfo/cmake> > -- *Please don't ask where I come from, It's a shame!* Best Regards Yuchen
-- 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
