[vtkusers] How do determine the minimal set of vtk libraries necessary

[Boxer, Aaron]

Will this handle objective c++ files?  Foo.mm file name, for example.

-----Original Message-----
From: Bill Lorensen [mailto:bill.lorensen at gmail.com] 
Sent: Thursday, January 30, 2014 8:00 AM
To: Boxer, Aaron
Cc: vtkusers at vtk.org
Subject: Re: [vtkusers] How do determine the minimal set of vtk libraries necessary

If you are using VTK6, there is a python script in:
VTK/Utilities/Maintenance/WhatModules.py
Run it without arguments and it will explain how to use it.


On Wed, Jan 29, 2014 at 11:24 PM, Boxer, Aaron <Aaron.Boxer at uhn.ca> wrote:
> Is there an easy way of finding the minimal set of static vtk 
> libraries that an application
>
> Needs in order to link?  Currently I am linking with all of them. I 
> suppose I could start
>
> Removing libraries one at a time and seeing if my app still compiles; 
> just wondering if there
>
> Is an easier way.
>
>
>
> Thanks,
>
> Aaron
>
>
> This e-mail may contain confidential and/or privileged information for 
> the sole use of the intended recipient.
> Any review or distribution by anyone other than the person for whom it 
> was originally intended is strictly prohibited.
> If you have received this e-mail in error, please contact the sender 
> and delete all copies.
> Opinions, conclusions or other information contained in this e-mail 
> may not be that of the organization.
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the VTK FAQ at:
> http://www.vtk.org/Wiki/VTK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtkusers
>



--
Unpaid intern in BillsBasement at noware dot com

This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient. 
Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. 
If you have received this e-mail in error, please contact the sender and delete all copies. 
Opinions, conclusions or other information contained in this e-mail may not be that of the organization.