-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Small fixes #21982
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Small fixes #21982
Conversation
nits: - remove extra configure-toolset.ps1|sh imports - remove duplicate `/v:$verbosity` addition to `msbuild` command line from build.sh
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
if (Test-Path $configureToolsetScript) { | ||
. $configureToolsetScript | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was old cruft. Sourcing tools.ps1 sources this file for us already and makes all settings available in this scope. Same for the similar block near the end of build.sh.
# Set verbosity | ||
echo "Setting msbuild verbosity to $verbosity" | ||
msbuild_args[${#msbuild_args[*]}]="-verbosity:$verbosity" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I didn't remove this, we end up with extra options on the msbuild
command line because tools.sh handles $verbosity
itself. Doesn't matter much but also doesn't help at all.
# Add default .binlog location if not already on the command line. tools.ps1 does not handle this; it just checks | ||
# $BinaryLog, $CI and $ExcludeCIBinarylog values for an error case. But tools.ps1 provides a nice function to help. | ||
if ($BinaryLog) { | ||
$bl = GetMSBuildBinaryLogCommandLineArgument($MSBuildArguments) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This and the similar for
loop in build.sh
are somewhat better than was here before. The scripts won't bother to add a /bl:Build.binlog
option if anything one starting with /bl:
or /binaryLogger:
(plus -bl:
or -binaryLogger:
in the build.sh case) already exists.
$BinaryLog