View Single Post
  #9  
Old 11-24-2014, 05:01 AM
raistlin raistlin is online now
Registered User
 
Join Date: 11-14-2008
Posts: 23
Thanks for the quickfix. I had it installed and it creates log files. Yay.

I have another question regarding the difference i see.

The logfile is generated at the script directory, c:\Builds\Source\BuildScripts:
Code:
c:\Builds\Source>visbuildcmd BuildScripts\Test.bld /mta /loglevel 0 /config BuildScripts\VisBuildPro.config LOGFILE=%PROJROOT%.log /nologo
24-11-2014 10:54:36: Starting Build: 'c:\Builds\Source\BuildScripts\Test.bld'
24-11-2014 10:54:36: Building project step 'Project steps'...
24-11-2014 10:54:36: Building project step 'Log Message'...
LOGFILE=Test.log
24-11-2014 10:54:36: Build successfully completed (elapsed = 00:00:00).
The logfile is generated at my current directory, c:\Builds\Source:
Code:
c:\Builds\Source>visbuildcmd BuildScripts\Test.bld /mta /loglevel 0 /config BuildScripts\VisBuildPro.config /LOGFILE %PROJROOT%.log /nologo
24-11-2014 10:55:12: Starting Build: 'c:\Builds\Source\BuildScripts\Test.bld'
24-11-2014 10:55:12: Building project step 'Project steps'...
24-11-2014 10:55:12: Building project step 'Log Message'...
LOGFILE=c:\Builds\Source\Test.log
24-11-2014 10:55:12: Build successfully completed (elapsed = 00:00:00).
Since you said LOGFILE macro and /logfile param are equivalent, the generated logfile path is a little inconsistent.

Last edited by raistlin; 11-24-2014 at 05:26 AM.
Reply With Quote