On Tue, Sep 2, 2014 at 1:03 PM, David Cole <dlrd...@aol.com> wrote: > > Ok, how does it sound if we have a variable, such as > > CMAKE_EXPORT_COMPILE_COMMANDS? > > Let's say, CMAKE_EXPORT_TARGETS_INFORMATION. > > > I would prefer CMAKE_EXPORT_TARGETS_FILE, or some name that implies it > is a filename value, with the value of the variable being the name of > the file to generate. > I think it's better to do an "ON/OFF" setting, given that from an IDE point of view what we want is to be able to run cmake again and get the file. If Eclipse generated the file I will still want to open it, and then we'd have to agree on a file name or need to modify the build directory, which kind of defeats the purpose.
> > Who's the consumer of this file? Is it just one particular IDE, or is > it meant to be general and possibly be used by multiple IDE generators? > (I'm not sure I fully understand the context of the intent here based > on the prior emails.... Can you explain it a little more?) > The consumer of this file is the IDE or anyone who needs to be able to figure out the project's data. We need ways to describe the targets generated by the project to let the IDE user know what targets the project has and to be able to use them. To get some context, let me define one of our use-cases, which would be a KDE user. To build a KDE Plasma 5 installation you need > 100 repositories to be built and configured. This means that all these are configured and installed to a prefix, possibly with an external tool. Our user will want to develop one of those projects. To do so, he will open the project and choose the build directory tied to it, from there we need to infer all the information he will need to develop the project. Here's where the targets file comes into place, the IDE will just need to open this file and the compile_commands.json files. If they're not created the IDE will set the cache values then generate to be able to access them. I hope it makes sense now. 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
