On 03.12.09 20:23:36, Rodolfo Lima wrote: > John Drescher escreveu: > > install screen > > Thanks for the tip but that's not my point in this whole thread (i.e. > I'm not looking for solutions, I'm giving one). > > CMake does so much complicate things to make working with software > projects a seamless experience across different platforms that I doubt > that automatically managing a symlink tree is such a huge effort. > > You know, there's workarounds for everything. Before cmake I wrote a gcc > wrapper to make its output look like what cmake does to it. If this > wasn't implemented in cmake and I come up with this idea, people would > say "but you can write a wrap to gcc to filter its output, why bother?". > > That's how I see some suggestions in this thread. IMHO cmake came to be > when people were sick of workarounds (like autotools) to manage > projects. So why resort to workarounds like we used to do when better, > seamless solutions exist? (I'm talking in the point of view of someone > that doesn't use IDE's).
Well, IMHO adding symlinks for source files to a _buildtree_ is exactly such a workaround. Its a workaround for editors (or users) that are not capable of editing in one dir and running make in a different dir. Andreas -- Your life would be very empty if you had nothing to regret. _______________________________________________ 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
