Hello, I'd like to define an INTERFACE library that has header files only but still generates its own project in Visual Studio. The only way to add headers to an interface target that I'm aware of is target_source_files(), which instead of creating a project it will cause the header files themselves to propagate to the actual targets that specify the interface target as a link dependency.
Is there a way to change this behavior? If not, the only workaround I can think of is pretty old-school: add_custom_target(), but if I use that I'm not sure I can specify include directories and preprocessor definitions that will be inherited by dependencies. So it seems like I'm forced to choose one or the other. -- 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
