aboutsummaryrefslogtreecommitdiff
path: root/src/httpserver.cpp
diff options
context:
space:
mode:
authorfanquake <[email protected]>2020-01-26 10:31:13 +0800
committerfanquake <[email protected]>2020-01-26 10:43:10 +0800
commitacd644b83d789a6cdfbeda19732119534d10058e (patch)
tree69aa7d2ff5236c2d1ddc4fa14943a77a1fed09eb /src/httpserver.cpp
parentMerge #18001: Updated appveyor job to checkout a specific vcpkg commit ID (diff)
downloaddiscoin-acd644b83d789a6cdfbeda19732119534d10058e.tar.xz
discoin-acd644b83d789a6cdfbeda19732119534d10058e.zip
build: remove --large-address-aware linker flag
This flag was used when building 32-bit Windows executables, which we no-longer do, and is not accepted by the linker for any of the hosts we currently build for. i.e: ```bash checking whether the linker accepts -Wl,--large-address-aware... no ``` --large-address-aware If given, the appropriate bit in the "Characteristics" field of the COFF header is set to indicate that this executable supports virtual addresses greater than 2 gigabytes. This should be used in conjunction with the /3GB or /USERVA=value megabytes switch in the "[operating systems]" section of the BOOT .INI. Otherwise, this bit has no effect. [This option is specific to PE targeted ports of the linker] You can check that the appropriate bit in the COFF header of our current Windows binaries is still be set using dumpbin. i.e: ```powershell dumpbin /headers .\bitcoind.exe FILE HEADER VALUES <snip> 26 characteristics Executable Line numbers stripped Application can handle large (>2GB) addresses ```
Diffstat (limited to 'src/httpserver.cpp')
0 files changed, 0 insertions, 0 deletions