Re: [chromium-dev] I can't compile chromium x64

[Peter Kasting]

I had an internal developer ask me about this last weekend.  I notice the d.c.o instructions page just changed a few days ago from saying "Windows 8.1 SDK" to "Windows 10 SDK"; I wonder if this SDK doesn't work in some scenarios (non-internal-hermetic toolchain?).

+CC scottmg who made this instruction change.

PK

On Wed, Dec 9, 2015 at 11:01 PM, Alexey Solovey <act...@gmail.com> wrote:

Hello. Why I can't compile chromium x64? 

- Windows 10 SDK installed. 

- Visual Studio 2013 installed. 

- WDK installed.

Get's this. 

[322/1004] CXX obj\chrome\browser\ui\views\tabs\browser_ui.window_finder_win.obj

FAILED: ninja -t msvc -e environment.x64 -- "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\amd64\cl.exe" /nologo /showIncludes /FC @obj\chrome\browser\ui\views\tabs\browser_ui.window_finder_win.obj.rsp /c ..\..\chrome\browser\ui\views\tabs\window_finder_win.cc /Foobj\chrome\browser\ui\views\tabs\browser_ui.window_finder_win.obj /Fdobj\chrome\browser_ui.cc.pdb

d:\chromium\src\chrome\browser\ui\views\tabs\window_finder_win.cc(223) : error C2065: 'IVirtualDesktopManager' : undeclared identifier

d:\chromium\src\chrome\browser\ui\views\tabs\window_finder_win.cc(223) : error C2923: 'base::win::ScopedComPtr' : 'IVirtualDesktopManager' is not a valid template type argument for parameter 'Interface'

d:\chromium\src\base\win\scoped_comptr.h(19) : error C2786: 'unknown-type' : invalid operand for __uuidof

d:\chromium\src\chrome\browser\ui\views\tabs\window_finder_win.cc(187) : error C2678: binary '->' : no operator found which takes a left-hand operand of type 'base::win::ScopedComPtr' (or there is no acceptable conversion)

        d:\chromium\src\base\win\scoped_comptr.h(150): could be 'base::win::ScopedComPtr<Interface,interface_id>::BlockIUnknownMethods *base::win::ScopedComPtr<Interface,interface_id>::operator ->(void) const'

        while trying to match the argument list '(base::win::ScopedComPtr)'

d:\chromium\src\chrome\browser\ui\views\tabs\window_finder_win.cc(187) : error C2039: 'IsWindowOnCurrentVirtualDesktop' : is not a member of 'base::win::ScopedComPtr'

        d:\chromium\src\base\win\scoped_comptr.h(20) : see declaration of 'base::win::ScopedComPtr'

d:\chromium\src\chrome\browser\ui\views\tabs\window_finder_win.cc(206) : error C2512: 'base::win::ScopedComPtr' : no appropriate default constructor available

d:\chromium\src\chrome\browser\ui\views\tabs\window_finder_win.cc(208) : error C2065: 'VirtualDesktopManager' : undeclared identifier

d:\chromium\src\chrome\browser\ui\views\tabs\window_finder_win.cc(208) : error C2660: 'base::win::ScopedComPtr<Interface,interface_id>::CreateInstance' : function does not take 1 arguments

[322/1004] CXX obj\chrome\browser\notifications\browser.platform_notification_service_impl.obj

ninja: build stopped: subcommand failed.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Scott Graham]

The error cited here is definitely the Win10 SDK not being found, but we're not entirely sure why. Bug is https://code.google.com/p/chromium/issues/detail?id=568201.

[Bruce]

I wonder if we should add an SDK version check to that file, to make the failure message more friendly?