Re: RES: [lazarus] Solution to the BIG compiled file issue!
On 16/01/2008, Christian U. [EMAIL PROTECTED] wrote: How difficult can it be to run strip? How difficult can it be to read the complete thread ??? 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. If I didn't understand this correct, I apologize in advance. Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: RES: [lazarus] Solution to the BIG compiled file issue!
Christian U. wrote: 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 _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: RES: [lazarus] Solution to the BIG compiled file issue!
Christian U. wrote: 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 ? It has all to do with what kind of info/settings you want in your release build. There is more than debug info only 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. Yes, however after a release, your not developing on that release anymore. Your users are using it and don't need to debug. The unstripped version you keep to yourself, so you can debug yourself. This thread is about stripping the debuginfos from LCL not from the user units. So the lcl needs to be compiles with some option. What has that to do with project settings ? Nothing. It's how the lcl should be build once. IIRC this discussion started about that. I agree that it would be a nice option to be able to choose between LCL with/without debuginfo FCL with/without debuginfo RTL with/without debuginfo OTOH, a debugger being able to use external symbols would solve it too. 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... You need them too if some error happens in the LCL (the LCL is not bugfree you know ?) Marc _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: RES: [lazarus] Solution to the BIG compiled file issue!
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
Re: RES: [lazarus] Solution to the BIG compiled file issue!
Yes, however after a release, your not developing on that release anymore. Your users are using it and don't need to debug. The unstripped version you keep to yourself, so you can debug yourself. Not in any case, stack traces can be very useful to find an problem on an exception but there only useful with debugionfos, so its an great thing to strip the lcl debuginfos but nit those from user code. So the lcl needs to be compiles with some option. What has that to do with project settings ? Nothing. It's how the lcl should be build once. IIRC this discussion started about that. I agree that it would be a nice option to be able to choose between LCL with/without debuginfo FCL with/without debuginfo RTL with/without debuginfo OTOH, a debugger being able to use external symbols would solve it too. I think one checkbox in the Build lazarus Configuration dialog is ok. RTL and FCL are never build while building lazarus its a bit hard to add an option for this i think. best regards Christian _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
RES: [lazarus] Solution to the BIG compiled file issue!
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 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? If I have problems, I point to Debug Path and the I can look for the error. []s Cesar Romero De: Fabio Dell'Aria [mailto:[EMAIL PROTECTED] Enviada em: terça-feira, 15 de janeiro de 2008 03:13 Para: lazarus@miraclec.com Assunto: Re: [lazarus] Solution to the BIG compiled file issue! Others benefits: 1)...speedup compilation (allocated less memory and write less bytes on disk). 2)...decreases Installation size; 3)...do not confuse new users with LCL code, during the debugging process. I think it can be set as an installation or a Project option (as in Delphi for the Use Debug DCUs compiler option)! -- Best regards... Fabio Dell'Aria. 2008/1/15, Fabio Dell'Aria HYPERLINK mailto:[EMAIL PROTECTED][EMAIL PROTECTED]: Hi Vincent, 2008/1/15, Vincent Snijders HYPERLINK mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]: Fabio Dell'Aria schreef: Hi to all, all we know how many new users do not uses lazarus because it create too BIG compiled files. We know that: 1)...the additional options are needed to can debug the project; 2)...just do a simple strip --strip-all filename reduce drastically the final size (an empty project go from 12.5Mb to 1.2 Mb). I think to have found a really simple solution to can continue to debug our project with a really little size increasing. Just remove all the debug-info from all the LCL object files to reduce the final compiled file from 12.5Mb to ONLY 2Mb (on Windows). We'll can continue to debug our projects but we'll CANNOT debug the LCL code. To obtain this little miracle just use the following command (from the shell): What do you think about? ;) irony Maybe not such a bad idea. Maybe we expect too much from our users. - That they know point 1) and 2) from above. - That they want to know why things go wrong in the LCL and can handle stepping though it, and prefer that above a list of hexdigits in their back traces. /irony IOW: I expect Lazarus users to be knowledgeable, Lazarus is not for fools. Vincent Yes I understand but why loose so many new users? All the programmers come from Delphi reports this issue and only a little subset of them check for a solution on Google. Others are lost! But if a solution exists why do not use it? I do not understand! :( _ To unsubscribe: mail HYPERLINK mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] with unsubscribe as the Subject archives at HYPERLINK http://www.lazarus.freepascal.org/mailarchives; \nhttp://www.lazarus.freepascal.org/mailarchives -- Best regards... Fabio Dell'Aria. No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.2/1224 - Release Date: 14/01/2008 17:39 No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.2/1224 - Release Date: 14/01/2008 17:39
RES: [lazarus] Solution to the BIG compiled file issue!
We need a native debugger support for FPC/Lazarus programs on all platforms.That's the big issue everyone seems to avoid talking about... I agree with you, and this is the kind of Project that I want to participate. []s Cesar Romero No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.2/1224 - Release Date: 14/01/2008 17:39 _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: RES: [lazarus] Solution to the BIG compiled file issue!
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 ? 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 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. Marc _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: RES: [lazarus] Solution to the BIG compiled file issue!
On 15/01/2008, Marc Weustink [EMAIL PROTECTED] wrote: 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 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. Some people are really taking this issue overboard. Like Marc said: When you create a release of your product you have do package you product - zip file, compile you help file etc, etc... Part of that process can be... TO RUN STRIP!!! ALL DEBUG INFORMATION WILL BE REMOVED! BUT WHILE YOU ARE DEVELOPING YOU NEED THAT DEBUG INFORMATION. How difficult can it be to run strip? Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: RES: [lazarus] Solution to the BIG compiled file issue!
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
Re: RES: [lazarus] Solution to the BIG compiled file issue!
Graeme Geldenhuys schrieb: On 15/01/2008, Marc Weustink [EMAIL PROTECTED] wrote: 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 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. Some people are really taking this issue overboard. Like Marc said: When you create a release of your product you have do package you product - zip file, compile you help file etc, etc... Part of that process can be... TO RUN STRIP!!! ALL DEBUG INFORMATION WILL BE REMOVED! BUT WHILE YOU ARE DEVELOPING YOU NEED THAT DEBUG INFORMATION. How difficult can it be to run strip? How difficult can it be to read the complete thread ??? _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
