Log level for console vs. log file

[raistlin]

Hi Kinook,

I have searched around in the forums to look for more information about how logging works and haven't found much concrete info about it.

In general, i read these 2 links below and still a little confused.
http://www.kinook.com/VisBuildPro/Ma...ildlogging.htm
http://www.kinook.com/VisBuildPro/Ma...putuseropt.htm

Last week i started to mess around with logging by minimizing the amount of logs produced by the console with /loglevel and succeeded. However the side effects of it were loosing the ability to log to file. I log file by passing LOGFILE macro to child bld scripts.

Is there anywhere that specifically says, which loglevel will / will not log to file? Thanks.

[kinook]

http://www.kinook.com/VisBuildPro/Ma...elproperty.htm

[raistlin]

Thanks. I used the link above for /loglevel. But how can i achieve /loglevel vbldLogLevelWarning + but still able to log with vbldLogLevelDetailed to LOGFILE?

[kinook]

Set Tools | Application Options | Logging (More) | Log level to Detailed and specify /loglevel 1 when calling visbuildcmd.
http://www.kinook.com/VisBuildPro/Ma...ingmoreopt.htm
http://www.kinook.com/VisBuildPro/Manual/consoleapp.htm

[raistlin]

Thanks Kinook. This works but it requires me to parse /logfile _filename_.

visbuildcmd Test.bld /loglevel 1 /logfile Test.log

I wish to use the LOGFILE macro already defined in the bld script, also when i parse LOGFILE macro in the command line, but omitting the /logfile parameter:

visbuildcmd Test.bld /loglevel 1 LOGFILE=%PROJDIR%\BuildLogs\%PROJROOT%.log

Is it possible? Thanks.

[kinook]

/logfile filename and LOGFILE=filename are equivalent. Both have the effect of defining a LOGFILE temporary macro which is available in the build.
http://www.kinook.com/VisBuildPro/Ma...ildlogging.htm
http://www.kinook.com/VisBuildPro/Ma...stemmacros.htm