[Insight-users] Visual 6.0 problems

[Luis Ibanez]

Hi Bradley,

You are doing the right thing,
ITK.dsw is the workspace file to load.

  VC++ is in fact NOT crashing !

What happens is that ITK has a large set of test programs
which are used for quality assurance.  We have about 250
test files that exercise the functionality of most of the classes.
That allows to rapidly detect bugs introduced in the code
when  new functionalities are added.

This is what you can see every day in ITK dashboard:

http://www.itk.org/Testing/Dashboard/MostRecentResults-Nightly/Dashboard.html

All these test are recompiled several times a day in about
ten different platforms.

There is a .dsp file for each one of these test, so what you
perceive as crashing (I assume that you refer to the fact
that VC++ freezes for a while) it is just the time that VC++
requires for loading all these tests.

Well, that's for the bad news...


Now, for the good news:  there are two ways in which
you can  avoid this long time for loading:

Option One:
In principle you don't need the testing. It is nice to have
because it allows you to make sure that the toolkit was
correctly built in your system.... but you can just build the
library.  In that case you can simply disable "BUILD_TESTING"
when you run CMake. That will prevent CMake from
creating all the .dsp files corresponding to tests.
You will still get the .dsp project files for the libraries and for
the examples.

Option Two:
This testing mechanisms has been replaced by the very
reason you are now concerned about:  The long time for
loading the ITK.dsw workspace.  
Right now all the tests are factorized in about six or seven
big test projects so the load time is much, much better.  
These changes was not done in the Beta release but in the
current version of the library. If you update your ITK code
by downloading the library using CVS, you will get these
new testing structure that loads nicely into VC++.


Option One is maybe the quick way of getting around
this problem while Option Two is probably your best bet
for the long term.


Hope that helps,


Luis

==================================

Erickson, Bradley J., M.D. wrote:

>ITK.dsw is what I load. WHen I do so, VC loads projects for perhaps a
>minute. But sometimes the compiler crashes in the middle of this. If it
>doesn't, and I do a 'build', it dies in various modules, but always with the
>same error: referenced memory that could not be "written". That seems like a
>bug in the compiler... I have a fairly powerful system, so shouldn't be
>resource limitations...
>
>By the way, thanks for the quick response!
>Brad
>
>-----Original Message-----
>From: Luis Ibanez [mailto:luis.ibanez@kitware.com]
>Sent: Thursday, April 04, 2002 12:14 PM
>To: Erickson, Bradley J., M.D.
>Cc: 'insight-users@public.kitware.com'
>Subject: Re: [Insight-users] Visual 6.0 problems
>
>
>Hi Bradley,
>
>Once you run CMake You should find a ITK.dsw
>file in the binary directory that you indicated
>during the configuration.
>
>This is the workspace that you should open,
>not any of the .dsp files.
>
>Please let us know if you find any problems
>loading this ITK.dsw file. In principle that
>should be very straightforward.
>
>
>Luis
>
>
>---------------------------------------------
>
>Erickson, Bradley J., M.D. wrote:
>
>>I just downloaded the beta pack. It compiled fine under LINUX, but the
>>visual C compiler crashes either while loading the ITK workspace, or while
>>compiling it. I realize the instructions say to load the ALL_BUILD
>>workspace, but what I have has nothing in it. What did I do wrong, and how
>>do I correct it?
>>THanks
>>Brad
>>_______________________________________________
>>Insight-users mailing list
>>Insight-users@public.kitware.com
>>http://public.kitware.com/mailman/listinfo/insight-users
>>
>>
>
>
>
>