sgraenitz added a comment. > No, everything is being built for android. Cross-compiling lldb-server > involves cross-compiling llvm libraries, clang libraries, and if you've got > swift in the picture, swift host libraries. LLVM and clang libraries are > built against the libc++ from the android NDK, but in standalone builds, LLDB > will try to link against the freshly built libc++ from LLVM. You get loads of > undefined references to symbols from the NDK's libc++.
For the `link_directories` line: if you cross-compile the entire tree and this tree contains libc++, wouldn't it be natural that LLDB will try to link against the freshly built libc++? If this is not your intention, then maybe we need a `LLDB_EXTERNAL_LIBCXX` option instead? CHANGES SINCE LAST ACTION https://reviews.llvm.org/D60180/new/ https://reviews.llvm.org/D60180 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
