Bug 230877 - [Win] WebCore.dir\Debug\WebCore.lib : fatal error LNK1248: image size (1000309F0) exceeds maximum allowable size (FFFFFFFF)
Summary: [Win] WebCore.dir\Debug\WebCore.lib : fatal error LNK1248: image size (100030...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: CMake (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2021-09-27 19:32 PDT by Fujii Hironori
Modified: 2021-11-08 11:47 PST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fujii Hironori 2021-09-27 19:32:34 PDT
[Win] WebCore.dir\Debug\WebCore.lib : fatal error LNK1248: image size (1000309F0) exceeds maximum allowable size (FFFFFFFF)

WinCairo Debug fails to build with CMake Visual Studio generator.
Ninja build has no problem.

> perl .\Tools\Scripts\build-webkit --wincairo --debug --no-ninja

> WebCore.dir\Debug\WebCore.lib : fatal error LNK1248: image size (1000309F0) exceeds maximum allowable size (FFFFFFFF) [C:\home\webkit\gb\WebKitBuild\Debug\Source\WebCore\WebCore.vcxproj]
Comment 1 Fujii Hironori 2021-09-27 19:37:33 PDT
I'm using Microsoft Visual Studio Professional 2019 Version 16.11.3.
Comment 2 Fujii Hironori 2021-09-27 21:20:46 PDT
I tried MSBuild+Clang-cl, and it can build with zillions of compilation warnings.

1. Install required components
  https://docs.microsoft.com/en-us/cpp/build/clang-support-msbuild

2. perl .\Tools\Scripts\build-webkit --wincairo --debug --no-ninja --cmakeargs="-T ClangCL"
Comment 3 Fujii Hironori 2021-09-29 18:43:29 PDT
I successfully built the latest AppleWin Debug (r283156) without Ninja on my PC. 😵

> perl .\Tools\Scripts\build-webkit --debug --no-ninja
Comment 4 Radar WebKit Bug Importer 2021-10-04 19:33:41 PDT
<rdar://problem/83867090>
Comment 5 Fujii Hironori 2021-10-19 23:36:54 PDT
Removing /Zc:lambda siwtch (reverting r283007) can compile WinCairo Debug.
Comment 6 Don Olmstead 2021-11-08 11:47:59 PST
Same issue occurs with VS 2022 17.0 that was released today.