Hello, What are the possible problem what we will encounter if we convert ITK's ImageIO modules to be shared libraries on Windows? And manage the gcc exported symbols why we are at it?
Performing the factory registration of ImageIO factory objects during static initialization in static libraries is fill with problems and tricky behaviors and is problematic for large applications to manage. By making these libraries shared the ImageIO factory objects should be unique and consistent across different libraries which use ITK, so that they will not get registered multiple times. Additionally, by explicitly specifying the exported symbols on gcc this should help to reduce the library size. Thanks for you thoughts, Brad _______________________________________________ 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://www.itk.org/mailman/listinfo/insight-developers
