[Insight-developers] Installation under Linux

[Lorensen, William E (Research)]

Maybe we should leave it be then. The alternative is not really acceptable
since users would have to know which filter is in which kit. For examples,
in vtk, I still have problems remembering where things are.

Bill,

-----Original Message-----
From: Bill Hoffman [mailto:bill.hoffman@kitware.com]
Sent: Friday, April 04, 2003 2:21 PM
To: Lorensen, William E (Research); 'Holmes, David R., Ph.D.'; Blezek,
Daniel J (Research); 'insight-developers@public.kitware.com'
Subject: RE: [Insight-developers] Installation under Linux


There would be quite a few files in that directory, and with all
the extra utilities that ITK uses, and the .txx files, it could become
a problem, and quite a mess.

Another alternative, would be to change the coding conventions slightly.

Instead of 
#include <itkObject.h>
#include <itkAcosImageFilter.h>

it would be:

#include <Common/itkObject.h>
#include <BasicFilters/itkAcosImageFilter.h>

This would allow us to have only one -I path, but leave all
the files in separate directories.   Vnl already takes this
approach.

In addition to avoiding directories with thousands of files, it
provides extra documentation to users.    Users would know
where to find classes used in a file just by looking at the
include directives.

-Bill



At 10:58 AM 4/3/2003, Lorensen, William E (Research) wrote:
>I agree with David and Dan. I just did an installation at a GE location and
>would have expected the include's and others to be in one directory. I
>believe the vtk install puts them in one place.
>
>Lets discuss briefly on this weeks t-con.
>
>Bill
>
>-----Original Message-----
>From: Holmes, David R., Ph.D. [mailto:Holmes.David3@mayo.edu]
>Sent: Thursday, April 03, 2003 10:21 AM
>To: 'Blezek, Daniel J (Research)';
>'insight-developers@public.kitware.com'; 'insight@public.kitware.com'
>Subject: RE: [Insight-developers] Installation under Linux
>
>
>Hi Dr Blezek-
>
>We have also had the desire to get all of the include files into one
>directory.  Right now, our make file is kind of a bear with all of the -I
>flags.  I started writing a script to do that for our project.  Actually,
we
>wanted to get a single include directory which could be used by all of the
>platforms because right now we have 6 copies of the same files around.  As
>far as we were able to tell there are only 3-6 platform specific files.
One
>is the itkConfigure.h and the others are in the vnl code.
>
>I also like your second suggestion.  So far, we have dug around into the
>makefiles generated by cmake for itk in order to find the flags.  Not real
>efficient, but it works.
>
>Hope all is well with you and your family.
>
>thanks
>
>david
>
>====================================================================
>David R Holmes III                            holmes.david3@mayo.edu
>Mayo Foundation                                 voice: (507)538-5503
>Rochester, MN                                     fax: (507)284-9171
>====================================================================
>
>>  -----Original Message-----
>>  From: Blezek, Daniel J (Research) [mailto:blezek@crd.ge.com]
>>  Sent: Thursday, April 03, 2003 8:55 AM
>>  To: insight-developers@public.kitware.com; 'insight@public.kitware.com'
>>  Subject: [Insight-developers] Installation under Linux
>>  
>>  Hi all,
>>  
>>    When I install Insight under Unix, I get this
>>  /usr/local/InsightToolkit/{Common,Numerics,Utilities,...}  requiring
>>  multiple -I flags on the command line (when not using CMake).  I have
two
>>  suggestions for folks like me who don't always use CMake:
>>  
>>  1)  Could all the .h and .txx files be put into
>>  /usr/local/InsightToolkit?
>>  Then I only need one -I flag in my makefile.  This is consistent with
>>  many
>>  other packages, and eases the burden for non-CMake users.
>>  
>>  2)  Could CMake write out any Insight specific flags in a "Readme.txt"
>>  type
>>  file?  I could then use those flags in my makefile, and still be
>>  compatible.
>>  This file could be placed in the install include directory.
>>  
>>    In part, this request to make Insight more "compatible" with the way I
>>  commonly do things under Unix, which I suspect is fairly common among
>>  Unix
>>  developers.
>>  
>>  Thanks,
>>  -dan
>>  
>>  --
>>  Daniel Blezek, Ph.D.
>>  blezek@crd.ge.com
>>  Visualization and Computer Vision Lab, Imaging Technologies
>>  GE Corporate Research & Development
>>  
>>  
>>  _______________________________________________
>>  Insight-developers mailing list
>>  Insight-developers@public.kitware.com
>>  http://public.kitware.com/mailman/listinfo/insight-developers
>_______________________________________________
>Insight-developers mailing list
>Insight-developers@public.kitware.com
>http://public.kitware.com/mailman/listinfo/insight-developers
>_______________________________________________
>Insight-developers mailing list
>Insight-developers@public.kitware.com
>http://public.kitware.com/mailman/listinfo/insight-developers