A. Awesome. Thanks kindly for posting this. This helps.
-Jordan
> On Jul 29, 2019, at 5:19 AM, Frederik Seiffert
> wrote:
>
> A quick semi-related update on this in case this useful to someone: in order
> to get Android Studio to locate debug information and resolve the
>
A quick semi-related update on this in case this useful to someone: in order to
get Android Studio to locate debug information and resolve the
"___lldb_unnamed_symbol" entries I needed to add "-Wl,--build-id=sha1" to the
LDFAGS. This is now fixed in our Android toolchain.
Frederik
> Am
Hi David,
> Looking at your backtrace, it appears that you're seeing the bug in BFD ld.
> With the -r option, it resolved the __start and __stop symbols early, then
> ended up with a .o file that caused everything declared in it to be dropped
> during final linkage. This results in anything
Hi,
On 01/07/2019 15:38, Frederik Seiffert wrote:
Thanks for the explanation David.
I believe there was a bug in clang where I didn't add an empty symbol
for compilation units that didn't contain any selectors. If you then
linked a program or a library that didn't contain any selectors
Thanks for the explanation David.
> I believe there was a bug in clang where I didn't add an empty symbol for
> compilation units that didn't contain any selectors. If you then linked a
> program or a library that didn't contain any selectors then you'd see this
> error at link time. This
On 01/07/2019 13:14, Frederik Seiffert wrote:
1. When using Qt to build a simple test app with Objective C, I’m
getting the following runtime error when launching the app:
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol
"__start___objc_selectors" referenced by
Hi,
I’ve been working on using a more up-to-date Clang with the Android toolchain
(in order to use the 2.0 Objective-C runtime), and managed to integrate the
Clang r353983 prebuilt into NDK r20.
While this seems to work well so far when targeting armeabi-v7a, I am getting
the following errors
