Skip to content

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

Merged
merged 2 commits into from
May 19, 2020
Merged

Small fixes #21982

merged 2 commits into from
May 19, 2020

Conversation

dougbu
Copy link
Contributor

@dougbu dougbu commented May 19, 2020

  • restore default "/bl" setting if $BinaryLog
  • correct the feeds to match latest recommendations

dougbu added 2 commits May 18, 2020 23:15
nits:
- remove extra configure-toolset.ps1|sh imports
- remove duplicate `/v:$verbosity` addition to `msbuild` command line from build.sh
@Pilchie Pilchie added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label May 19, 2020
@dougbu
Copy link
Contributor Author

dougbu commented May 19, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@dougbu dougbu requested a review from a team May 19, 2020 21:42
@dougbu dougbu marked this pull request as ready for review May 19, 2020 21:42
if (Test-Path $configureToolsetScript) {
. $configureToolsetScript
}

Copy link
Contributor Author

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"

Copy link
Contributor Author

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)
Copy link
Contributor Author

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.

@dougbu dougbu merged commit 4420a7d into master May 19, 2020
@dougbu dougbu deleted the dougbu/allow.logging branch May 19, 2020 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants