Well, that sounds like the perfect way to use ExternalProject.
But why do you want to show the sources in Visual Studio? Just for ease of looking at them?
As I said in my earlier reply... even if we showed the sources, editing them would not trigger a rebuild of the external project. The dependencies are tracked via custom commands and stamp files that indicate last successful run time of those custom commands. They are not tracked by Visual Studio on a per-source-file/per-obj-file basis as they are in a normal VS project.
The main goal of ExternalProject is to provide an easy-to-use way of *building*, *installing* and depending on an external project... It is most definitely NOT to provide an easy way to do active development on a project.
If you need to see the sources for something that you're building within Visual Studio, then to me, that's a big red flag that it should not be an external project.
HTH, David C. -- 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://www.cmake.org/mailman/listinfo/cmake
