Re: [cmake-developers] Restriction on target types for GraphViz dependency graph generation

[Daniel Pfeifer]

On Wed, Dec 16, 2015 at 5:20 AM, Andrey Mishchenko  wrote:
> Hi,
>
> I noticed that the automatic dependency graph generation in CMake targeting
> GraphViz only considers targets of certain types. In particular, it only
> adds nodes for executables and shared, static, and module libraries.
>
> Is this deliberate?

There are open issues about that:

https://cmake.org/Bug/view.php?id=13809
https://cmake.org/Bug/view.php?id=15636
https://cmake.org/Bug/view.php?id=15638

> If I submit a patch extending this functionality to (optionally, via
> configuration variables) work with more target types, would it be received
> well?

Absolutely. Thanks for working on this!

-- Daniel
-- 

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

Re: [cmake-developers] Restriction on target types for GraphViz dependency graph generation

[Attila Krasznahorkay]

Hi Andrey,

I would be extremely happy with an extension to this functionality.

Right now I have way too many targets in my projects to make good sense of them 
if all of them are put into a single graph. If I would be able to specify that 
I'd like to see the connections between all the targets with names ".*Pkg$" for 
instance, that could be very nice.

Cheers,
   Attila

> On 16 Dec 2015, at 05:20, Andrey Mishchenko  wrote:
> 
> Hi,
> 
> I noticed that the automatic dependency graph generation in CMake targeting 
> GraphViz only considers targets of certain types. In particular, it only adds 
> nodes for executables and shared, static, and module libraries.
> 
> Is this deliberate?
> 
> If I submit a patch extending this functionality to (optionally, via 
> configuration variables) work with more target types, would it be received 
> well?
> 
> Andrey Mishchenko
> -- 
> 
> 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

-- 

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

[cmake-developers] Restriction on target types for GraphViz dependency graph generation

[Andrey Mishchenko]

Hi,

I noticed that the automatic dependency graph generation in CMake targeting
GraphViz only considers targets of certain types. In particular, it only
adds nodes for executables and shared, static, and module libraries.

Is this deliberate?

If I submit a patch extending this functionality to (optionally, via
configuration variables) work with more target types, would it be received
well?

Andrey Mishchenko
-- 

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