Re: Why would release static lib be significantly larger then my debug build?
Tech-Archive recommends: Fix windows errors by optimizing your registry
I have a VS2005 static library project of unmanaged C++ code. When I
compile and link, I noticed that my debug lib is 2668K and the release
build is over 16K. Why would release static lib be significantly larger
than my debug build?
It's not by the figures you've shown - unless you meant to say the
release build is 16K larger than the debug version?
Release is using /MD and Debug /MDD
Should that be /MDd ?
Debug information is disabled in release, NDEBUG is defined,
optimization is set to speed, browse information is set to none.
You may see a difference if you set the optimisation to size rather
than speed.
Dave
.
Relevant Pages
- Why would release static lib be significantly larger then my debug build?
... When I compile and link, I noticed that my debug lib is 2668K and the release build is over 16K. ... Release is using /MD and Debug /MDD for runtime libraries. ... (microsoft.public.vc.language) - Re: create custom audio source filter for Windows Mobile
... I cannot create any class based on CSource and ... strmbasd.lib is the debug version, ... The WindowsMobile SDK only comes with the ... release lib but with .h files that reference the debug lib ... (microsoft.public.win32.programmer.directx.video) - Re: debugging in release mode
... I have no doubt that it's a problem of mine and not of the compiler. ... I don't really need optimization ... for the sake of memory space or execution speed. ... shows the differences between the default debug mode and the default release ... (microsoft.public.vc.mfc) - RE: Step by Step skips large chunks of code
... project settings it is in debug mode and no optimization is set. ... We have several similar projects that debug fine, ... Microsoft Online Community Support ... (microsoft.public.vsnet.debugging) - Re: Downside of using Debug builds for production
... use of Microsoft's Exception Handling application block. ... the process if I desire to debug the application. ... For example, an "optimized" build could in some cases be larger than the "non-optimized" build, depending on what the optimization goals are. ... it seems to me that you are really only interested in one aspect of the "debug" build: the inclusion of symbols allowing for the stack trace to include line numbers in the exceptions. ... (microsoft.public.dotnet.framework) |
|