This is how I understand it.... LCL is built with debug inforation.
You executable uses LCL and is also set to include debug information
by default. This equals a huge executable. That is what you want
while developing. When you create a release version of you product,
you run strip agains the executable. It removes ALL debug
information, even those carried over from LCL! You end up with a
executable the same size as if you compiled your executable with LCL
without debug information.
I say it again, this thread was about stripping the debug infos from lcl
code not from the whole executable.
It is real good to have debug infor from your code to have function
names in stack traces that can be very helpful.
But thers no need for the lcl debug inso so if it is stripped per default
- we have not so many users that ask for the executable size,
- the debugger dont jumps in lcl code that is not interesting for most
users,
- you musnt use strip and have an good usage from stack traces.
best regards
Christian
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
