|
no. I use batch file scripts. where I basically do the following. Delete All DCU's, (including all 3rd party libraries) Compile Each application. Delete all dcus again. I have had so many problems with delphi linking in wrong dcu code etc (more under 2005, than D7) that I now use the command line only for proper building. the IDE is essentially just a glorified text editor in my opinion, and is only good to have compiling for the syntax checking. I just link a batch file to my tools menu to compile my projects. and trap the console messages for hints and warnings using console piping. I built four in a row exes. and it was always the exact identical token locations that differed. perhaps because I am rebuilding all the code. If you are linking dcu's in that already existed. ie 3rd party. then the exe records datestamps of the units inside the exe (i think) which might account for more differences Rohit Gupta wrote: Are you compling from the IDE? I find that the differences are greater when I use the commandline compiler. And unfortunately thats what I use for distribution versions.Date sent: Thu, 21 Jul 2005 14:47:43 +1200 From: Kyley Harris <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], NZ Borland Developers Group - Delphi List <[email protected]> Subject: Re: [DUG] Exe contents Copies to: Send reply to: NZ Borland Developers Group - Delphi List <[email protected]> <mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> [ Double-click this line for list subscription options ] Well. You are right about the exe being slightly different. in the case of my exes the difference is allways in the exactly the same place, and there are a series of repeating tokens that are 2 bytes each, which are different. as though it is a date stamp, or symbol table token or something. I do remember way back in the days of DOS Turbo Pascal that the help said you always have to rebuild the MAP table for each EXE. so i guess you are not doing this because its a massive file to distribute. What are you using the MAP table to do? have you tried just compiling memcheck into your program with td32 symbols turned on? it logs all memory leaks and errors, with class type, and call stack information to show you the exact line of code leaking, no need for a map table. 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 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
