In WPF's builds, Build.binlog goes under $(ArtifactsDir)Log\$(Configuration) as if it were part of an AnyCPU build.
tools.ps1:
[$LogDir = Join-Path (Join-Path $ArtifactsDir "log") $configuration]
Our builds are entirely arch-specific, and always set /p:Platform=x86 or /p:Platform=x64. We would like to get build logs to be redirected to appropriate folders that encode $(Plaform) when one is set (and !='AnCPU').
The current state of affairs prevents us from even attempting parallel dev-builds of more than one architecture. For e.g., we can't try to build x86 and x64 simultaneously on a dev box because the msbuild (bin)logs share the same file and therefore clash.
In an ideal world, we'd be able to pass -platform to build.ps1 (just like we can set -configuration today) and have it come out the other side with /p:Platfrom= along with all the right fixups for various folders under $(ArtifactsDir).
/cc @tmat, @chcosta
/cc @dotnet/wpf-developers
In WPF's builds, Build.binlog goes under
$(ArtifactsDir)Log\$(Configuration)as if it were part of anAnyCPUbuild.tools.ps1:Our builds are entirely arch-specific, and always set
/p:Platform=x86or/p:Platform=x64. We would like to get build logs to be redirected to appropriate folders that encode$(Plaform)when one is set (and!='AnCPU').The current state of affairs prevents us from even attempting parallel dev-builds of more than one architecture. For e.g., we can't try to build
x86andx64simultaneously on a dev box because the msbuild (bin)logs share the same file and therefore clash.In an ideal world, we'd be able to pass
-platformtobuild.ps1(just like we can set-configurationtoday) and have it come out the other side with/p:Platfrom=along with all the right fixups for various folders under$(ArtifactsDir)./cc @tmat, @chcosta
/cc @dotnet/wpf-developers