Welcome, Guest
Username: Password: Remember me
General discussions, feature requests for CodeTyphon Project and discussions that don't fit in any of the other specific CodeTyphon forum categories.
  • Page:
  • 1

TOPIC:

Executable files enormous 9 years 1 month ago #6930

  • gustavo tolson
  • gustavo tolson's Avatar Topic Author
  • Offline
  • New Member
  • New Member
  • Posts: 13
  • Thank you received: 0
First I want to thank you for making Code Typhon available to all with the same spirit of those at FreePascal.
I have a question regarding the size of executable fiies compiled using Typhon 4.8. I have written several applications using Delphi 3 to 7 using my own libraries for graphic output using TImage and descendants. In Windows and in Linux, my executable files comiled using Delphi tend to range in size between 800-950Kb and 1100-1500Kb, respectively.
When I compile similar files I've recently ported to Typhon, the executable files are 7.5 and 10 Mb in size, respectively (i.e. a factor of about 9 bigger), despite the fact that I have used the {$SMARTLINK ON} general directive on all units (including those included in CodeTyphon). Further, there was no change in size with or without the {$SMARTLINK ON} directive. This latter point, in particular, I don't understand.
Can you tell me what is going on?
Thanks in advance for your kind attention to this matter.

Please Log in or Create an account to join the conversation.

Executable files enormous 9 years 1 month ago #6932

  • Sternas Stefanos
  • Sternas Stefanos's Avatar
  • Offline
  • Moderator
  • Moderator
  • Ex Pilot, M.Sc, Ph.D
  • Posts: 4512
  • Thank you received: 1101
Sir
first of all my suggestion is to use always the latest CodeTyphon (5.2 now)

When I compile similar files I've recently ported to Typhon, the executable files are 7.5 and 10 Mb in size
Do you have debugging info in your project ?
CT by default store application debugging info in to executable

In Project Options=>Debugging
you can find more options like
-"Use external gdb debug symbols file". In this case ALL debugging info stored to external file NOT in executable file
-"Strip" debugging info/symbols from executable
-Use "Build Modes".




and finally always you can use CTCenter=>Tools=>Strip Tool
to remove debugging info from executables,
just drag-and-drop the file to dialog and hit "do Strip" button



We must write a debugging wiki...
PilotLogic Architect and Core Programmer

Please Log in or Create an account to join the conversation.

Last edit: by Sternas Stefanos.

Executable files enormous 9 years 2 weeks ago #7030

  • gustavo tolson
  • gustavo tolson's Avatar Topic Author
  • Offline
  • New Member
  • New Member
  • Posts: 13
  • Thank you received: 0
Dear Sternas,
thanks for your thorough answer.
I am not using version 5.2 because I've had quite a bit of trouble installing it, particularly on one of my computers. Also, I don't like the new tab-formatted interface of the source and form editor.
I still don't understand why the ($SMARTLINK ON} general directive had no effect on the resulting executable file size.
I will get back to you when I try your fixes.
Thanks again.

Please Log in or Create an account to join the conversation.

  • Page:
  • 1