|
From: Per W. <pw...@ia...> - 2002-09-17 16:25:15
|
When compiling with debug information on, every new include file results in larger executable. windows.h isn't any include file. It is THE include file. It continues to include a lot of other windows files. /Per W On Tue, 17 Sep 2002, The Tone'ster wrote: > > hi, > > noob here again. > > I notice that simply doing a #include <windows.h> increases my executable size > by some 250k without touching any functions in my code within WIN32. > > Again, I am a Java programmer, so I am trying to get my head around how this > stuff works. > > Is this increase in size due to needing a larger 'text' segment for all of the > stuff defined in <windows.h> and the 5 zillion #includes it pulls in ? > > Or ... is this because libs or something are getting statically linked into the > executable ? > > TIA, > Tony > > ===== > > > > ------------------------------------------------------- > Sponsored by: AMD - Your access to the experts on Hammer Technology! > Open Source & Linux Developers, register now for the AMD Developer > Symposium. Code: EX8664 http://www.developwithamd.com/developerlab > _______________________________________________ > Dev-cpp-users mailing list > Dev...@li... > TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users > |