Issues compiling on Windows 10
kristof-mattei opened this issue · 2 comments
kristof-mattei commented
[12711/17070] CXX obj/services/resource_coordinator/public/interfaces/interfaces_internal_shared_cpp_sources/interfaces_internal_shared_cpp_sources_jumbo_1.obj
FAILED: obj/services/resource_coordinator/public/interfaces/interfaces_internal_shared_cpp_sources/interfaces_internal_shared_cpp_sources_jumbo_1.obj
d:/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe ../../build/toolchain/win/tool_wrapper.py cl-wrapper ninja -t msvc -e environment.x64 -- "c:\program files (x86)\microsoft visual studio\2017\enterprise\vc\tools\msvc\14.13.26128\bin\hostx64\x64/cl.exe" /nologo /showIncludes @obj/services/resource_coordinator/public/interfaces/interfaces_internal_shared_cpp_sources/interfaces_internal_shared_cpp_sources_jumbo_1.obj.rsp /c gen/out-x64/static_library/gen/services/resource_coordinator/public/interfaces/interfaces_internal_shared_cpp_sources_jumbo_1.cc /Foobj/services/resource_coordinator/public/interfaces/interfaces_internal_shared_cpp_sources/interfaces_internal_shared_cpp_sources_jumbo_1.obj obj/services/resource_coordinator/public/interfaces "interfaces_internal_shared_cpp_sources_cc.pdb"
gen/out-x64/static_library/gen/services/resource_coordinator/public/interfaces/interfaces_internal_shared_cpp_sources_jumbo_1.cc(9): fatal error C1083: Cannot open include file: '../../../../../../../services/resource_coordinator/public/interfaces/memory_instrumentation/memory_instrumentation.mojom-shared.cc': No such file or directory
I have the latest version of depot_tools.
Visual Studio 15.7.1 (2017).
Anything that is missing?
NicolasLacombe commented
Hello,
Same issue here, on master branch. Chromium seems to be building fine on the same machine though. Any insight?
Visual Studio 15.6.7.
[edit] Branch "chromium-upgrade/66" is fine.
MarshallOfSound commented
Hey there,
It's been a long time coming but the libchromiumcontent repository is being archived as it is no longer used in the Electron build system (🎉 this is a good thing).
If your issue is still relevant to Electron in it's current build system (please verify first) then you should probably raise a similar issue on electron/electron.
Thanks 😄