> For the moment, I like swiftc over swift because it seems a lot > simpler. I hope this means the least changes for CMake right now.
I need to correct myself on this. While I like swiftc for looking simpler, I'm actually thinking swift might be fewer changes since the file-by-file thing is what CMake does today. It may turn out swift is easier to figure out in the end too when we eventually look at add_library and linking them (since we can reverse engineer from the Xcode logs). But either way, both of them seem to need SOURCES. Thanks, Eric -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
