[Insight-developers] Too Many Projects in the default ITK build

[William A. Hoffman]

There is an option to the SUBDIRS command in cmake, EXCLUDE_FROM_ALL.

 Any
 directories after the EXCLUDE_FROM_ALL marker will not be included in
 the top level makefile or project file.  This is useful for having
 cmake create makefiles or projects for a set of examples in a project.
 You would want cmake to generated makefiles or project files for all
 the examples at the same time, but you would not want them to show up
 in the top level project or be built each time make is run from the
 top.

It may be that we want to use that option.  Then make sure all the examples
are built as part of the testing structure, so the get coverage and we make
sure the build.   But when users build a project for ITK, they are not included
in the ITK project.  To build an individual test, a use would have to cd into
the directory of the test and run make or load the visual studio project. 

But, we can talk at the TCON.

-Bill

At 10:47 AM 5/13/2005, Stephen R. Aylward wrote:
>The nice part about examples is that they are already grouped by chapter in the software guide.  The testing-grouping would intuitively match the chapter group.  With appropriate documnetation in the software guide (e.g., a "how to use this book and its code" chapter), perhaps building via the test mechanism is sufficient?
>
>I will try to join today's tcon, but I have double-booked that time, and Julien is out of town.
>
>Stephen
>
>Lorensen, William E (Research) wrote:
>>Actually, the examples are built twice. For testing purposes we use the test driver. They are also built to create single executables that can be run as they are described in the user manual.
>>We should discuss this at today's t-con.
>>Bill
>>-----Original Message-----
>>From: insight-developers-bounces+lorensen=crd.ge.com at itk.org
>>[mailto:insight-developers-bounces+lorensen=crd.ge.com at itk.org]On Behalf
>>Of William A. Hoffman
>>Sent: Friday, May 13, 2005 9:57 AM
>>To: insight-developers at itk.org
>>Subject: [Insight-developers] Too Many Projects in the default ITK build
>>
>>I think it is time to clean up the number of projects in ITK.
>>The test driver system was created to avoid this problem.   Basically,
>>with the IDE builds you get too many projects.   Visual studio sort of
>>handles the load, but it is very sluggish.  XCode just uses up all available
>>memory and crashes.  Right now by default when you run cmake on ITK, you
>>get 333 projects!   I am surprised that MS dev can handle it.
>>
>>Here is the break down of where things are coming from:
>>With examples and testing on (default): 333 projects
>>With examples and testing off:  29 projects
>>With examples on and testing off:  293 projects
>>With testing on and examples off:  69 projects
>>So, it would seem that the culprit is the Examples, which adds an
>>additional 264 projects to ITK!  
>>I think we need to take the same approach as we did with the test driver,
>>with the examples.   A test driver can contain 50 or so programs.  So,
>>if we do the same thing for examples, then the 293 would drop to about 5 projects.
>>I think the target we should shoot for is no more than 100 projects in ITK.
>>The fewer the better of course.
>>
>>-Bill
>>_______________________________________________
>>Insight-developers mailing list
>>Insight-developers at itk.org
>>http://www.itk.org/mailman/listinfo/insight-developers
>>_______________________________________________
>>Insight-developers mailing list
>>Insight-developers at itk.org
>>http://www.itk.org/mailman/listinfo/insight-developers
>
>-- 
>===========================================================
>Dr. Stephen R. Aylward
>Associate Professor of Radiology
>Adjunct Associate Professor of Computer Science and Surgery
>http://caddlab.rad.unc.edu
>aylward at unc.edu
>(919) 966-9695
>_______________________________________________
>Insight-developers mailing list
>Insight-developers at itk.org
>http://www.itk.org/mailman/listinfo/insight-developers