chromium/src
0
Fork 0
Code Activity
Files
db5d04637f1e6c059f56f505e2e66e6ea6e17ea1
src/docs/windows_split_dll.md
Nico Weber c36b015eb4 Remove is_multi_dll_chrome. 
No behavior change.

Bug: 1056290
Change-Id: Ic7c1de0e00f86d3941f65f8856eb1baf66667dfb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154725
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760296}
2020-04-18 03:12:46 +00:00

893 B
Raw Blame History

Windows Split DLLs

A build mode where chrome.dll is split into two separate DLLs. This was undertaken as one possible workaround for toolchain limitations on Windows.

We removed support for this again after the toolchain limitations were fixed, see https://crbug.com/726150.

How

Split DLL used to be controlled by the is_multi_dll_chrome gn variable.

Details

This forcible split was implemented by putting .lib files in either one DLL or the other, and causing unresolved externals that result during linking to be forcibly exported from the other DLL. This works relatively cleanly for function import/export, however it cannot work for data export.

Some more details can be found on the initial commit of the split_link script https://src.chromium.org/viewvc/chrome?revision=200049&view=revision and the associated bugs: https://crbug.com/237249 https://crbug.com/237267.