Heh, I remember with VB4 that was the norm. The executable came out differently (size and contents) each time you built to disk depending on the contents of some internal heap VB4 kept. For the smallest executable size they recommended you close VB4, open it up again and do a build to disk immediately. Brilliant!
Would surprise me if that was the case with Delphi though... David. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kyley Harris Sent: Thursday, 21 July 2005 10:48 a.m. To: [EMAIL PROTECTED]; NZ Borland Developers Group - Delphi List Subject: Re: [DUG] Exe contents I hate to say it. but that sounds ridiculous if it is true. I will be testing that later, because It would also make the purpose of patch installs very difficult. Are the EXE sizes different? or just the content? Rohit Gupta wrote: >Using D7, I find that if I delete all dcus and compile the app and >then I recompile it with no changes then the exes are wildly >different. The 3rd compile only has minor differences (presumably >time related). I know that this did not happen with earlier versions. > >Is this a feature ? It causing us headaches in that we can not >reliably match the map file with the error that the user is reporting. >The map file changes wildly to match the exe. >Regards > >Rohit > >==================================================== >================== >CFL - Computer Fanatics Ltd. 21 Barry's Point Road, AKL, New >Zealand >PH (649) 489-2280 >FX (649) 489-2290 >email [EMAIL PROTECTED] or [EMAIL PROTECTED] >==================================================== >================== > > >_______________________________________________ >Delphi mailing list >[email protected] >http://ns3.123.co.nz/mailman/listinfo/delphi > > > _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
