Added some debug printToString() methods that will make it easy to dump current configurations to a log to help facilitate tracking stuff down. For now I'm just adjusting the RT_VERBOSE_DEFAULT flag at the top of CompilerMSVC as the BuildSettings are constructed from the stuff inside the magic new macros. Hopefully later on we'll have an easy way to set that at runtime from the outside but this is working now I think for basic debugging.
It's pretty verbose, we do levels, though it seems like for debugging purposes a lot of this can be useful. one thing I'm noticing is that the BuildSettings structure gets called 3 or 4 times at startup, and as I'm logging from there you get this dump each time. I imagine we can reduce that.
Output currently ends up looking like (for me, on the project I'm debugging):
Added some debug
printToString()
methods that will make it easy to dump current configurations to a log to help facilitate tracking stuff down. For now I'm just adjusting theRT_VERBOSE_DEFAULT
flag at the top of CompilerMSVC as theBuildSettings
are constructed from the stuff inside the magic new macros. Hopefully later on we'll have an easy way to set that at runtime from the outside but this is working now I think for basic debugging.It's pretty verbose, we do levels, though it seems like for debugging purposes a lot of this can be useful. one thing I'm noticing is that the
BuildSettings
structure gets called 3 or 4 times at startup, and as I'm logging from there you get this dump each time. I imagine we can reduce that.Output currently ends up looking like (for me, on the project I'm debugging):