[Insight-developers] compiling tests, include problems

[Damion Shelton]

Ok... so maybe the solution is to allow tests in any directory to include
files from any and all of the allowable ITK include paths. I think this
actually makes sense, because as the toolkit evolves, there are bound to be
tests of other classes that need to include files from multiple directories
(basicfilters, common, statistics, etc.) in order to do a meaningful.

For instance, it is certainly possible to write a test that exercises blox
objects without relying on basicfilters files, but this test wouldn't be
much of a true test; in order to perform one, I need a source of data via
spatial functions (from common) and a way to perform blurring and edge
detection (from basicfilters).

Is there a compelling reason _not_ to allow tests to include any ITK file
they want to?

-Damion-

> Careful...  I think the test may have to be in BasicFilters but I don't
> want to get in a mode of transferring files from Common to BasicFilters
> just so that we can test them.