[Insight-users] Re: ITK1.8 increased space?

[Miller, James V (Research)]

Vincent, 

You might want to check into building RelWithDebInfo instead
of both Release and Debug.  You can setup a RelWithDebInfo
build by adding RelWithDebInfo to your CMAKE_CONFIGURATION_TYPES (should be
an advanced option
in CMakeSetup).

CMAKE_CONFIGURATION_TYPES:STRING=Debug;Release;RelWithDebInfo

RelWithDebInfo uses most of the compiler optimization of
Release but also have enough Debugging information so that
you can find out why a program crashed.  It also has
enough debugging information so that you can run 
memory checking software like Purify or performance 
checking software like Quantify.

I almost exclusively use a RelWithDebInfo build.  The 
execution times are fast but when something crashes I 
can usually figure out why.  Since RelWithDebInfo is
an optimized build, not all variables will be available
in the debugger (some variables get optimized away). But
the call stack is usually in pretty good shape so that 
you can at least know the line of code where the program
crashed.

I can do about 95% of my debugging on a RelWithDebInfo
build.  The last 5% of the time, I have to break down 
and build a debug version.

Jim


-----Original Message-----
From: Vincent Luboz [mailto:Vincent.Luboz at imag.fr]
Sent: Wednesday, November 10, 2004 5:38 PM
To: Luis Ibanez
Cc: Insight-users at itk.org
Subject: Re: [Insight-users] Re: ITK1.8 increased space?


Hi Luis

I am using VisualStudio .Net 2003 Windows XP and I built ITK in release and
in 
debug versions. Your numbers are right, in release version, ITK occupies
1.6GB.
But since I also compiled in Debug, ITK reached 6GB.
All the warping (TCL, Java...) was disabled
Since the Debug version is pretty useful, I am going to keep it.
Thanks again for your help,

Vincent.

Quoting Luis Ibanez <luis.ibanez at kitware.com>:
> 
> Hi Vincent
> 
> Thanks for pointing this out.
> 
> This is actually useful information.
> 
> 6 GigaBytes sounds a bit excesive for a build of ITK.
> 
> Here are some numbers from our local builds, that include
> Examples ON and Testing ON, building for Release:
> 
>    1) 1.6 GigaBytes in VisualStudio .Net 2003 Windows XP
>    2) 1.2 GigaBytes in GCC 3.3 under Linux Debian
> 
> 
> You may want to double check that you didn't enabled any of the
> wrappings (Tcl, Python or Java), and that you are building only
> for Release or only for Debug (if you are using MS-Windows...).
> Otherwise that will duplicate the disk usage.
> 
> 
> If you are in Windows, you may find useful to try the
> application "Treesize":
> 
>         http://www.tucows.com/preview/195999.html
> 
> in order to figure out where the disk space is being
> taken per directory.
> 
> 
> If you are in Unix, you can simply do "du" in the binary directory
> where you build ITK.
> 
> 
> 
> Please let us know what you find,
> 
> 
> 
>    Thanks
> 
> 
>       Luis
> 
> 
> 
> -----------------------------
> Vincent.Luboz at imag.fr wrote:
> 
> > Hi Luis
> > 
> > I didn't put this message on the itk list because it's not useful for
the 
> > list, I think...
> > I just installed ITK1.8, with build examples ON, build shared library
OFF
> and 
> > build testing ON. It results in a repertory of:
> > 6 Go and 18 000 files
> > By comparison, ITK1.6 with the same configuration was only:
> > 700 Mo and 12 000 files
> > Is it normal?
> > 
> > Vincent
> > 
> > 
> > -------------------------------------------------
> > envoye via Webmail/IMAG !
> > 
> > 
> > 
> 
> 
> 
> 
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk.org
> http://www.itk.org/mailman/listinfo/insight-users
> 




-------------------------------------------------
envoye via Webmail/IMAG !

_______________________________________________
Insight-users mailing list
Insight-users at itk.org
http://www.itk.org/mailman/listinfo/insight-users