Back to General and Gameplay Programming

very small win32 programs with vc++.

trigger · 2001-07-06T07:57:29

hi all! just some days ago i compiled a program with an empty WinMain function. *shock* totally 24kb exe file only for an empty WinMain program!? after asking on irc i found out that there are some helpfull linker settings that dont linke the not needed stuff. so the exe file shrinked from 24kb to 16kb. when i use upx with the 16kb version i can get the file size down to ~4kb ! the only problem is that i cant really understand how this linker options work! is there anybody out who can explain them to me!? i also got, that when you use that linker option you have to specify the wanted libs or dlls manually. anybody out there who can tell me wich libs are important and why they are???? so you see that i am really interested in how it works and not only in using some linker options somebody told me to use. best regards trigger

General and Gameplay Programming Programming

Started by trigger June 26, 2001 03:41 PM

24 comments, last by trigger 22 years, 9 months ago

Beer Hunter

712

July 03, 2001 10:33 PM

avianRR: Anything in the libraries that are not used by your program will simply not be placed in the executable when it is generated. Removing unused libraries will speed up linking time, but have no effect on file size.

alexmoura

450

July 04, 2001 12:00 AM

Ok - exactly why this obsession about reducing the size of a 24k program anyway?

You know, I never wanted to be a programmer...

Alexandre Moura

trigger

123

Author

July 04, 2001 02:36 AM

lo all!

why this obsession about reducing the size of a 24k program anyway? - simple question. its needed for a little 64k intro. every free byte is needed so i need to get all possible ones

!

best regards
trigger

http://trigger.xenyon.net/

NuffSaid

122

July 05, 2001 02:57 PM

/FILEALIGN:512 is the same is /OPT:NOWIN98. At least, thats what I got from the docs.

The effects of UPX will be even more scary when you get the memory runtime size in kilobytes (or Megabytes), instead of percentages of system resources.

That''s because most of us developers have hundreds of megs of ram installed, and a 2% increase on our machines may actually be a very big jump for the end user''s machine.

==========================================In a team, you either lead, follow or GET OUT OF THE WAY.

Beer Hunter

712

July 05, 2001 06:54 PM

Nuffsaid: I agree. 2% of my memory is about 4.5 megs. Sorry if I sounded sarcastic or anything in my last post - that wasn''t my intention.

Makes me wonder what the decompressor''s doing.

NuffSaid

122

July 06, 2001 07:57 AM

quote:Original post by Beer Hunter
Nuffsaid: I agree. 2% of my memory is about 4.5 megs. Sorry if I sounded sarcastic or anything in my last post - that wasn''t my intention.

Makes me wonder what the decompressor''s doing.

I would have taken offence, if only I wasn''t that sarcastic myself

I have no idea what the decompressor is doing. Maybe if you looked at the source code, you''d get an idea...

==========================================In a team, you either lead, follow or GET OUT OF THE WAY.

very small win32 programs with vc++.

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

very small win32 programs with vc++.

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines