On Mon, Sep 1, 2014 at 9:26 PM, David Cole <dlrd...@aol.com> wrote: > The approach looks reasonable, but having it unconditionally spit out a > file in cmGlobalGenerator regardless of generator is probably not what we > want. Seems like it should be based on a variable, or be in a specific > generator, or somehow have a limited scope. > > HTH, > David C. >
Ok, how does it sound if we have a variable, such as CMAKE_EXPORT_COMPILE_COMMANDS? Let's say, CMAKE_EXPORT_TARGETS_INFORMATION. Aleix
-- 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
