WIP: Add support for conditionally building with ITKFactoryRegistration #851
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit is NOT ready for integration or review. It depends on #852
This commit introduces option Slicer_USE_ITKFactoryRegistration allowing
to conditionally build with ITKFactoryRegistration. Since latest version
of ITK is expected to address IOFactory issues originally fixed by
introducing ITKFactoryRegistration library, this new option will allow
to easily build Slicer and test that it effectively works without it.
List of SlicerExecutionModel changes: