> Well, the problem is the size of the exe file. ;-) > > When I am working on a project I usually want to generate debug > > information for debugging. > > But when I give the generated file to someone else I surely do not need > > this information in the exe file anymore. > > So why should I be forced to search for ways to delete this information > > from the exe if there could be a way to avoid this hassle? > > There is no need to search for ways to delete this information, you need > only a proper workflow: exes compiled for distribution shall be compiled > with release settings which means: > - no debug info > - symbols fully stripped > - full optimization (which would make debugging harder) > - asserts ignored > - custom debug code ignored > - ... > Using debug and release settings is something very basic when working on > software being deployed to others. > > This is interesting, I'd had never actually thought of a work flow like this. So, would you have 2x different projects? 1 with as dubug and the 2nd as release, or is there a better way of doing it?
Richard
-- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
