[Insight-developers] Musings on new modularization

[Brad King]

On 03/14/2011 11:46 AM, Jim Miller wrote:
> ITK/ITK/Core/Common/src/foo.txx
[snip]
> ITK/ITK/Core/Common/include/foo.h

For ".h" and ".txx" both should be in include.  Only ".cxx" goes in src.
This approach makes install rules easy to do automatically.  Everything
in "include/" is part of the public interface and gets installed.

> Brad, can you comment on this some more? Are you anticipating the custom
> vendor-specific packages to be parallel to the inner ITK directory (and
> under the outer ITK directory)? 
> 
> Would this be managed at the repository level where the inner or outer
> ITK directory would be a submodule? What would be your recommendation as
> to how to structure a project that provides custom-modules against ITK?

One of the goals of modularization is to make it easy to add custom
modules to ITK and produce a custom distribution.  With the current
layout that can be done by just creating a local branch from ITK and
adding the custom modules in a new directory.  The current modularization
infrastructure will pick up the new directory automatically with no changes
to the CMake code.  Then one can update ITK just by merging from upstream.

-Brad