Hi Brad I guess the “fast” way is to just wrap it, like ImageSourceCommon. Then just open a ticket on JIRA so that we can think about it. We may have to find a way not to wrap privatly inherited classes, which should be doable. I’m still working on the python 3 support which is taking some time, so I will not have much time to spend on this right now.
Michka > On 08 Dec 2014, at 21:19, Bradley Lowekamp <blowek...@mail.nih.gov> wrote: > > Michka, > > I just saw this new warning for this funky class I added: > > > > /scratch/dashboards/Linux-x86_64-gcc4.8-WrapITK/ITK-build/Wrapping/Modules/ITKCommon/itkImageToImageFilterA.xml: > warning(4): ITK type not wrapped, or currently not known: > itk::ImageToImageFilterCommon > > http://open.cdash.org/viewBuildError.php?type=1&buildid=3603076 > <http://open.cdash.org/viewBuildError.php?type=1&buildid=3603076> > > This class is privately inherited, and should not need to be directly > used/wrapped. However the similar ImageSourceCommon is explicitly wrapped > [1]. How sure what's best for the WrapITK interface. > > Brad > > > [1] > https://github.com/InsightSoftwareConsortium/ITK/blob/master/Modules/Core/Common/wrapping/itkImageSource.wrap > > <https://github.com/InsightSoftwareConsortium/ITK/blob/master/Modules/Core/Common/wrapping/itkImageSource.wrap>
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Kitware offers ITK Training Courses, for more information visit: http://kitware.com/products/protraining.php Please keep messages on-topic and check the ITK FAQ at: http://www.itk.org/Wiki/ITK_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/insight-developers
