Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Logging Delphi Compilations 1

Status
Not open for further replies.

Stretchwickster

Programmer
Apr 30, 2001
1,746
GB
Is there a way to keep a log of every compilation/build done in Delphi 6, and perhaps log the time it takes to compile/build the source code?

Anyone got any ideas how I could capture this information? A pointer in the right direction would be much appreciated.

Clive [infinity]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"To err is human, but to really foul things up you need a computer."
Paul Ehrlich
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To get the best answers from this forum see: faq102-5096
 
Clive. Isnt the info you wantin the Linker map file, must admit I havn't tried it.

Steve
Time for a new sig a bit of DNA I think will scan books and get back to you.
 
Thanks for the suggestion Steve, but the linker map file is overwritten each time Delphi is compiled and it doesn't give any compile/build time.

I need to be able to log the number of times Delphi compiles/builds and the time per compilation/build. Any ideas?

Clive [infinity]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"To err is human, but to really foul things up you need a computer."
Paul Ehrlich
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To get the best answers from this forum see: faq102-5096
 
Thank you Tonhu - you've given me a lead in the right direction!

Clive [infinity]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"To err is human, but to really foul things up you need a computer."
Paul Ehrlich
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To get the best answers from this forum see: faq102-5096
 
Fact is, I once wrote a build program for a client that did just that. The trick is to use the IDE just for DEV and debugging. Once satisfied with your code, open a command prompt window and call the command-line compiler to do your final build. One advantage to this is that you can have a different dot cfg file to do the build. For example, I always have RangeCheck ON in the IDE, but not in my project.cfg file, since it bloats the size of the exe. From the command line (or in my case the build program) call DCC32 and pipe the output to a file. Example: “C:\Delphi5\bin\dcc32 –B Project1 > ver487.log” Your compiler output will be preserved in file “ver467.log”

HTH
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top