Mirror of forum.nim-lang.org

8567 :: asyncdispatch on android

• seves (orginal) [2021-10-30T10:35:54+02:00] view original

  I'm trying to get a websocket client ("ws") to work on an android and get E / libc ++ abi: terminating.

  Now know that asyncdispatch is causing problems. With a simple async program without any net connection, there is already this error. Does anyone have any experience of you? Or an idea what I could try or do?

---

• yglukhov (orginal) [2021-10-30T16:00:57+02:00] view original

  Termux command line apps should work just as well as on any other platforms. Android UI apps are a bit trickier, because they have their own runloop in the main thread, and Android doesn't like main thread being blocked for more than a couple of seconds (or the app will be terminated), and asyncdispatch.runForever() or asyncdispatch.waitFor() effectively block the thread, so I assume that's what you're observing. So to fix this, you could either:

  • move async stuff to a secondary thread with its own runForever/waitFor
  • or attach asyncdispatch epoll descriptor to main thread's ALooper, and call drain (iirc) when the descriptor is triggered, so that main thread is never blocked.

---

• seves (orginal) [2021-10-30T18:07:44+02:00] view original

  Thanks @yglukhov,

  I suspect more and more that it's because of the libraries i use. I have now tried -DANDROID_STL= c++_ shared and c++_static and also played around with both build.gradle and CMakeList.txt, but unfortunately I can't get certain functions to work. These are: Files IOs, Net, ...

---

• yglukhov (orginal) [2021-10-30T18:35:16+02:00] view original

  Ok, you could improve my guessing by telling how exactly it doesn't work. Is it a ui app or termux, does it compile (errors?), does it crash (stack trace?), do you see any errors in logcat, does it not do what it should (how?).

---