diff options
| author | 2019-02-28 15:52:05 -0800 | |
|---|---|---|
| committer | 2019-03-20 21:07:47 +0000 | |
| commit | 3c21c0b1d9bab0d51100ca03aa157a1d8545c2ea (patch) | |
| tree | f249d66cfe8c40623633602c9dcb72a4364d8661 /java/java_test.go | |
| parent | 967511a4e844e439ab18cf0e77f2d406cc88d3be (diff) | |
Enable lld for windows
Bug: http://b/110800681
The following flags that the binutils linkers support are not available
in lld for Windows:
  -soname
  --no-undefined
  -rpath
Windows also uses "import libraries", which are stub libraries used only
for linking.  The binutils linkers accepted a DLL and treated them as an
import library.  But lld issues the following error:
  lld-link: error: ...DLL: bad file type. Did you specify a DLL instead
  of an import library?
To resolve this, pass '-out-implib=libFoo.a' to lld when linking
libFoo.dll.  Add libFoo.a as an implicit output to the 'ld' build rule.
Rewrite the shared libraries for a library/binary to use the import
library instead of the DLL.  As a side-effect, this also (correctly)
uses the AdbWinApi.a that's alongside
development/host/windows/prebuilt/usb/AdbWinApi.dll
Test: Run Windows tests (go/android-llvm-windows-testing) and check
absence of regressions.
Change-Id: I15a178589aa6882caa6e7e38650cc6ef48109764
Diffstat (limited to 'java/java_test.go')
0 files changed, 0 insertions, 0 deletions