On Mon, Dec 7, 2009 at 1:04 PM, steve naroff <snar...@apple.com> wrote: > Thanks for your comments Oscar. > > Our current thinking is to post process the cmake generated files and remove > all the absolute paths (since the project files are simply text). Since > cmake is a black box to me (and I am unfamiliar with it's generated 'code'), > it's unclear if this a 'good' idea? Or will I bump into other gotcha's? > > Any advice is appreciated...you have a lot more experience with this than I > do!
Steve, if that was a good idea, CMake would be doing that by default instead of using absolute paths, don't you think? As Eric pointed out, you must add CMake to your compiler build chain. It's one more tool (and with no third-party dependencies), like the C preprocessor, the C compiler and the linker. We did that at work and it's no big deal, people are so happy with the pro's of CMake over our former buildsystem (Visual C++ projects for Windows and Makefiles for Unix, which required twice the amount of maintainance work), they are not looking back. -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) _______________________________________________ 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
