Building using SDK version 15063.674 causes an error with mc.exe
Reported by
jtsil...@gmail.com,
Jan 9 2018
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Steps to reproduce the problem: 1. install Windows SDK 15063.674 2. build chromium developer build with default target 3. What is the expected behavior? Build should be successful What went wrong? /e/jtsillas/Work/workspace3/src ((HEAD detached at 64.0.3282.0)) $ ninja -C out/Release ninja: Entering directory `out/Release' [20433/68895] ACTION //remoting/host/win:messages(//build/toolchain/win:win_clang_x86) FAILED: gen/remoting/host/win/remoting_host_messages.h gen/remoting/host/win/remoting_host_messages.rc C:/Python27/python.exe ../../build/win/message_compiler.py environment.x86 -h gen/remoting/host/win -r gen/remoting/host/win -u gen/remoting/host/win/remoting_host_messages.mc mc.exe output different from files in E:\jtsillas\Work\workspace3\src\build\win\..\..\third_party\win_build_output\mc/remoting/host/win, see c:\users\jtsillas\appdata\local\temp\3\tmpdey1yg Did this work before? N/A Chrome version: 64.0.3282.0 Channel: n/a OS Version: Windows Server 2012 R2 Flash Version:
,
Jan 10 2018
Thanks for filing this bug - I didn't even know that 10.0.15603.674 had been released. Where did you get it? I can't find it on the archive page. Unfortunately mc.exe only prints out 10.0.15063 (the least-significant digit of the version is omitted) so two versions that produce different results will have matching version numbers displayed. Awesome. We should probably try to support this new 10.0.15063 version of mc.exe. On the upside, it looks increasingly likely that we will never bother supporting the Fall Creators Update SDK (10.0.16299) so that saves some effort.
,
Jan 10 2018
Can you zip up that temp folder and attach it to this bug?
,
Jan 10 2018
Thanks for filing the issue! This issue seems to be out of scope for triaging from ET end as it seems to be related to build. Hence , adding label TE-NeedsTriageHelp for further investigation.
,
Jan 10 2018
I'm not sure where it came from unfortunately. I believe one of our MSDN subscribers downloaded it from the Microsoft MSDN site ( https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk). But now I see it has been superseded by 16299.91. And the archive doesn't have it. There's a chance the same problem happens with 16299.91. We originally had this SDK installed and I'm pretty sure I was seeing it. We then uninstalled this 16299.91 and installed 15063.674. The problem was still there. Finally we went with the correct version which is 15063.468 (obtained from https://developer.microsoft.com/en-us/windows/downloads/sdk-archive). The problem went away with this SDK version.
,
Jan 10 2018
,
Jul 6
We now require 10.0.17134.0 so this bug is no longer applicable. If you hit problems with the new SDK please file a new bug. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by eostroukhov@chromium.org
, Jan 9 2018