Marc Weustink schrieb:
Cesar Liws Gmail wrote:
I Agree with you Fabio, and also it can be implemented in Lazarus:
1) Debug Path – LCL with Debug info
2) Release Path – LCL WITHOUT Debug Info
What if I want other options in my release ?
Assertions on/off or Rangechecking on/off ?
what has this todo with the lcl debugionfo ?
When Im writing my software I do not want to debug Lazarus, so why
should I include 10MB of LCL debug Info in my .EXE?
Then when you release, run strip
NO its not possible to debug then anymore. i think this is sayed 10
times in this thread.
This thread is about stripping the debuginfos from LCL not from the user
units.
See it as part of your release. Lazarus won't zip the exe for you
neither. It wont make an installer. ect. etc.
So see it as part of a release process.
Its good to habe debuginfos in an release also for stack traces on
exceptions and so on but no need for lcl debuginfo in an release exe...
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
