Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

On Wed, Feb 17, 2016 at 10:59 PM, Stephen Kelly wrote: > On 02/15/2016 07:24 PM, Tobias Hunger wrote: > > Hi Dominik, > > Am 15.02.2016 19:01 schrieb "Dominik Haumann" : >> 1. Wouldn't it make sense you have a developer sprint ASAP for this? > > I'd be in,

Re: [cmake-developers] CMake daemon for user tools

On Sun, Jan 10, 2016 at 12:10 PM, Stephen Kelly wrote: > > Hello, > > I've been working on adding a daemon mode for cmake to provide > information to user tools - such as IDEs - about the buildsystem. > > Following the discussion about providing metadata for IDEs to consume >

[cmake-developers] Linked library paths

Hi, I need to get the linked libraries of a target. I was moving the code away from get_target_property to generator expressions that should get into a generated file, although I haven't managed yet. Is there any possibility to do that already? I've been thinking of adding something like a map

Re: [cmake-developers] Generating buildsystem metadata from CMake

On Sat, Apr 18, 2015 at 11:56 AM, Stephen Kelly steve...@gmail.com wrote: Stephen Kelly wrote: The aim is to generate a structured file containing metadata relating the buildsystem. I've been quiet on this thread for a while, so I think it is time for an update. I became more ambitious

Re: [cmake-developers] Generating buildsystem metadata from CMake

On Sat, Mar 14, 2015 at 10:02 AM, Stephen Kelly steve...@gmail.com wrote: On Saturday, March 14, 2015, Aleix Pol aleix...@kde.org wrote: On Wed, Mar 11, 2015 at 11:10 AM, Stephen Kelly steve...@gmail.com wrote: Hi, Following from the thread here: http://thread.gmane.org

Re: [cmake-developers] Generating buildsystem metadata from CMake

On Wed, Mar 11, 2015 at 11:10 AM, Stephen Kelly steve...@gmail.com wrote: Hi, Following from the thread here: http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/10711/focus=12394 http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/10711/focus=12650 I'm

Re: [cmake-developers] Extracting target metadata, IDE integration

On Fri, Aug 29, 2014 at 4:20 AM, Aleix Pol aleix...@kde.org wrote: Dear cmake'rs, I'm rewriting the KDevelop plugin from scratch to fetch the information from the build directory. Now in the first implementation I'm using the compile_commands.json file that cmake already can generate

Re: [cmake-developers] Extracting target metadata, IDE integration

On Wed, Mar 4, 2015 at 9:05 PM, Brad King brad.k...@kitware.com wrote: On 03/02/2015 09:10 PM, Aleix Pol wrote: I created a new version of the patch: http://proli.net/meu/kdevelop/0001-cmake-Add-option-to-generate-target-metadata-for-IDE-v2.patch Thanks. Samples: LLVM: https

Re: [cmake-developers] Extracting target metadata, IDE integration

On Fri, Aug 29, 2014 at 4:20 AM, Aleix Pol aleix...@kde.org wrote: Dear cmake'rs, I'm rewriting the KDevelop plugin from scratch to fetch the information from the build directory. Now in the first implementation I'm using the compile_commands.json file that cmake already can generate

Re: [cmake-developers] Extracting target metadata, IDE integration

On Sat, Feb 14, 2015 at 1:02 PM, Stephen Kelly steve...@gmail.com wrote: Aleix Pol wrote: Hi guys, It's been since August with this. I understand we're all busy but this step is important for KDevelop as well as for other IDE's and I wouldn't like this to rot. Please, let's keep it moving

Re: [cmake-developers] Extracting target metadata, IDE integration

On Thu, Feb 5, 2015 at 6:03 PM, Aleix Pol aleix...@kde.org wrote: On Mon, Feb 2, 2015 at 5:36 PM, Aleix Pol aleix...@kde.org wrote: On Mon, Jan 26, 2015 at 9:15 PM, Tobias Hunger tobias.hun...@gmail.com wrote: I gave this patch a try with the cmake project data. I had hoped that this file

Re: [cmake-developers] Extracting target metadata, IDE integration

On Mon, Feb 2, 2015 at 5:36 PM, Aleix Pol aleix...@kde.org wrote: On Mon, Jan 26, 2015 at 9:15 PM, Tobias Hunger tobias.hun...@gmail.com wrote: I gave this patch a try with the cmake project data. I had hoped that this file would contain all the information an IDE might need

Re: [cmake-developers] Extracting target metadata, IDE integration

On Mon, Jan 26, 2015 at 9:15 PM, Tobias Hunger tobias.hun...@gmail.com wrote: I gave this patch a try with the cmake project data. I had hoped that this file would contain all the information an IDE might need, but there seems quite a bit missing for that. E.g. there is no information on

Re: [cmake-developers] Extracting target metadata, IDE integration

On Tue, Jan 20, 2015 at 3:47 PM, Brad King brad.k...@kitware.com wrote: On 12/18/2014 09:02 PM, Aleix Pol wrote: I would like to propose this as a final version of this patch. http://proli.net/meu/kdevelop/0001-cmake-Add-option-to-generate-target-metadata-for-IDE.patch For reference

Re: [cmake-developers] Extracting target metadata, IDE integration

On Thu, Jan 8, 2015 at 5:42 PM, Anton Makeev anton.mak...@jetbrains.com wrote: Aleix Pol aleixpol@... writes: I'd really appreciate your feedback on the patch I provided, I'll be happy to provide the information you miss. Aleix Aleix, could you please point me to the most recent patch

Re: [cmake-developers] Extracting target metadata, IDE integration

On Thu, Sep 25, 2014 at 9:14 AM, Anton Makeev anton.mak...@jetbrains.com wrote: Hey everyone, We are developing CLion at JetBrains that utilizes CMake as its main project model. Stephen Kelly timely drew our attention to this discussion, and I’d like to share some thoughts. Here are the

Re: [cmake-developers] Extracting target metadata, IDE integration

On Tue, Dec 23, 2014 at 1:30 AM, Aleix Pol aleix...@kde.org wrote: On Thu, Sep 25, 2014 at 9:14 AM, Anton Makeev anton.mak...@jetbrains.com wrote: Hey everyone, We are developing CLion at JetBrains that utilizes CMake as its main project model. Stephen Kelly timely drew our attention

Re: [cmake-developers] Extracting target metadata, IDE integration

On Fri, Oct 3, 2014 at 3:52 PM, Rolf Eike Beer e...@sf-mail.de wrote: Brad King wrote: On 10/01/2014 07:46 PM, Aleix Pol wrote: I'm very interested in getting this in and iterating forward. Any comments? How do changes get integrated? My main concern is that the format has

Re: [cmake-developers] Extracting target metadata, IDE integration

On Thu, Oct 2, 2014 at 2:43 PM, Brad King brad.k...@kitware.com wrote: On 10/01/2014 07:46 PM, Aleix Pol wrote: I'm very interested in getting this in and iterating forward. Any comments? How do changes get integrated? My main concern is that the format has not been proven

Re: [cmake-developers] Extracting target metadata, IDE integration

On Wed, Sep 24, 2014 at 6:51 PM, Aleix Pol aleix...@kde.org wrote: On Wed, Sep 24, 2014 at 3:55 PM, Brad King brad.k...@kitware.com wrote: On 09/22/2014 07:15 PM, Aleix Pol wrote: { version: 1.0, targets: [...] } Yes. The version number could either be maintained as its own thing

Re: [cmake-developers] Extracting target metadata, IDE integration

On Fri, Sep 26, 2014 at 1:27 AM, Stephen Kelly steve...@gmail.com wrote: Aleix Pol wrote: Hi, Here's another iteration of the patch [1]. Thanks for this. Can you tell me why exportName is part of the output? http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/10711/focus

Re: [cmake-developers] Extracting target metadata, IDE integration

On Wed, Sep 24, 2014 at 3:55 PM, Brad King brad.k...@kitware.com wrote: On 09/22/2014 07:15 PM, Aleix Pol wrote: { version: 1.0, targets: [...] } Yes. The version number could either be maintained as its own thing, or just the CMake version number could be used. Either way the Help

Re: [cmake-developers] Extracting target metadata, IDE integration

On Fri, Sep 19, 2014 at 7:44 PM, Brad King brad.k...@kitware.com wrote: On 09/18/2014 08:10 PM, Aleix Pol wrote: I added a CMAKE_OUTPUT_PROJECT_TARGETS variable that can be used to enable the generation of the file. I also renamed the file to ProjectTargets.json. http://www.proli.net

Re: [cmake-developers] Extracting target metadata, IDE integration

On Mon, Sep 8, 2014 at 2:51 PM, Brad King brad.k...@kitware.com wrote: On 09/03/2014 12:12 PM, Aleix Pol wrote: On Wed, Sep 3, 2014 at 5:48 PM, Alexander Neundorf wrote: I still don't understand why this shouldn't be an additional ExtraGenerator. Because it's not possible to change

Re: [cmake-developers] Extracting target metadata, IDE integration

On Tue, Sep 2, 2014 at 3:58 PM, David Cole dlrd...@aol.com wrote: It makes sense. But what IDE are you referring to? Eclipse? Some other concrete example? Or just any IDE and this feature should work everywhere CMake works...? I'm working on KDevelop, I know for a fact though, that other

Re: [cmake-developers] Extracting target metadata, IDE integration

On Tue, Sep 2, 2014 at 9:45 PM, Alexander Neundorf neund...@kde.org wrote: On Tuesday, September 02, 2014 09:58:37 David Cole via cmake-developers wrote: It makes sense. But what IDE are you referring to? Eclipse? Some other concrete example? Or just any IDE and this feature should work

Re: [cmake-developers] Extracting target metadata, IDE integration

On Wed, Sep 3, 2014 at 5:48 PM, Alexander Neundorf neund...@kde.org wrote: On Wednesday, September 03, 2014 12:30:21 Aleix Pol wrote: On Tue, Sep 2, 2014 at 3:58 PM, David Cole dlrd...@aol.com wrote: It makes sense. But what IDE are you referring to? Eclipse? Some other concrete example

Re: [cmake-developers] Extracting target metadata, IDE integration

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,

Re: [cmake-developers] Extracting target metadata, IDE integration

On Fri, Aug 29, 2014 at 4:20 AM, Aleix Pol aleix...@kde.org wrote: Dear cmake'rs, I'm rewriting the KDevelop plugin from scratch to fetch the information from the build directory. Now in the first implementation I'm using the compile_commands.json file that cmake already can generate

Re: [cmake-developers] Extracting target metadata, IDE integration

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,

[cmake-developers] Extracting target metadata, IDE integration

Dear cmake'rs, I'm rewriting the KDevelop plugin from scratch to fetch the information from the build directory. Now in the first implementation I'm using the compile_commands.json file that cmake already can generate for some time. It works quite well already, given how data just comes out ready

Re: [cmake-developers] Improving GraphViz output, clustering

On Mon, Sep 16, 2013 at 7:39 PM, Aleix Pol aleix...@kde.org wrote: Hi, I've been trying to get a good outlook of the internal dependencies of one of our projects (KDE Frameworks 5). One thing that I've found useful is adding clustering to external dependencies that, while needed

[cmake-developers] Improving GraphViz output, clustering

Hi, I've been trying to get a good outlook of the internal dependencies of one of our projects (KDE Frameworks 5). One thing that I've found useful is adding clustering to external dependencies that, while needed in the graph, having them grouped as a separate entity is desirable. Attached, I'm

Re: [cmake-developers] Improving GraphViz output, clustering

On Mon, Sep 16, 2013 at 10:03 PM, Alexander Neundorf neund...@kde.orgwrote: On Monday 16 September 2013, Aleix Pol wrote: On Mon, Sep 16, 2013 at 7:39 PM, Aleix Pol aleix...@kde.org wrote: Hi, I've been trying to get a good outlook of the internal dependencies of one of our projects