c36b015eb4
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}
23 lines
893 B
Markdown
23 lines
893 B
Markdown
# 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.
|