I prefer to use Inno Setup and compress the program inside the install routine itself. It is for downloading purposes and to minimize server load and download times that you want to compress it. It really doesn't matter how big or small the executable is once it is installed. If that is done, compression can still be done afterwards if so desired. I am trying to simply see why so much space is being used to remove what might not be necessary. Some people are answering with ways to compress the Delphi EXE. Is there a reason why my executable has to remain 5 times larger? Or are there some simple ways to cut down a significant chunk of the executable size? I do understand that Delphi 2009 is completely Unicode (which is the main reason why I upgraded), and being Unicode can cause up to a doubling of size. The executable it produced was only 2,671 KB while incorporating the same two components and basically having the same code as my current version. Prior to using Delphi 2009, I was using Delphi 4. When I build my production version, using the "Release" build configuration, the executable file produced is 13,533 KB. I use two components: LMD Innovative's ELPack and Sergey Tkachenko's TRichView that are compiled into my executable. I have no external DLLs or resources that I need for the program to run. I release a single executable (.EXE) for a desktop program using Delphi 2009.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |