[Insight-developers] checked in changes vis a vis new SystemTools ...

[Bill Hoffman]

Thanks for making the change.   

The idea was to create a library that could be shared by
VTK, ITK, and cmake.   So, it has some of its own naming conventions.
Specifying the sub-dir in the include, was to make sure that we could
mix ITK and VTK versions of the kwsys library.
So, you could have, something like this:

---someitk.h-----
#include <itkkwsys/SystemTools.hxx>

--- somevtk.h-----
#include <vtkkwsys/SystemTools.hxx>

--- vtk/itk program.cxx---
#include <someitk.h>
#include <somevtk.h>

They could even have different versions of the kwsys library.

We were also thinking, that each project might have its own additions
to the systems tools class, and that we might want to create a
itk::SystemTools : public itkkwsys::SystemTools  class that has
itk specific functions.   (for example, some of the cmake functions were
removed because they were really specific to cmake.)


Of course, right now, cmake and VTK do not use the library, but that
will come in time.


-Bill




At 03:14 PM 4/10/2003, Kent Williams wrote:
>I yanked out all of the file system utility calls in Code/IO/itkIOCommon, and 
>moved a couple that didn't already have an implementation in 
>itkkwsys/Systemtools, and then changed all the files that used to depend on 
>IOCommon so they use SystemTools.
>
>I'll keep watching the continuous builds to make sure I haven't broken 
>anything, but I did compile everything, and run all the tests.
>
>Some stylistic quibbles --
>
>1. The headers in itkkwsys are the only ones with '.HXX' extensions
>2. We don't normally have to add a subdirectory path in includes, e.g.
>
>#include <itkkwsys/SystemTools.h>
>
>3. should it be itkSystemTools.h? Is this a special case, or was that an 
>oversight?
>
>_______________________________________________
>Insight-developers mailing list
>Insight-developers@public.kitware.com
>http://public.kitware.com/mailman/listinfo/insight-developers