Re: Help to resolve issue in building PJSIP Android library

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



And another thing,did  you built CSipSimple, or PJSIP?

On Thu, Aug 4, 2016 at 12:46 PM, Nahum Nir <hello.shalom.hi@xxxxxxxxx> wrote:
Seems like an Android link problem. Either some lib wasn't build or the Android path not includes all PJSIP libs.

On Thu, Aug 4, 2016 at 12:14 PM, Monica Memane <monica.memane@xxxxxxxxxx> wrote:
Hi,

         We were successful in building the library on Mac platform.

We are referring the CSimple app to establish a call.We are creating and registering a local SIP user.
However we are getting the following error while initializing psua.create()-

java.lang.UnsatisfiedLinkError: Couldn't load pjsua2 from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/android.test.runner.jar", zip file "/data
/app/com.csipsimple-1.apk"],nativeLibraryDirectories=[/data/app-lib/com.csipsimple-1, /vendor/lib, /system/lib]]]: findLibrary returned null

We suspect that we must be missing some step in initialization of psua.



On 8/1/2016 5:59 PM, Nahum Nir wrote:
It will be faster to install a VM with linux and build....

On Mon, Aug 1, 2016 at 1:18 PM, Monica Memane <monica.memane@xxxxxxxxxx> wrote:

Hello PJSIP team,

We are trying to build the PJSIP Android library on Windows7 using Cygwin for one of our Android Application.
We are facing the following issues during compilation:
1. Compilation termination issues for step-
    $ make dep
2. "Undefined reference to pj_ files" for -
    $ make dep && make clean && make

Please find the attached log files.


We also tried to build the PJSIP Android library on Mac OS El Capitan
1. Successfully built PJSIP Android library for TARGET_ABI-armeabi .
 However we faced "Unsatisfied Link" issue when tried to run the sample application pjsua on Android device.
We assume that the possible cause might be conflict of device architecture.
2. We tried to use TARGET_ABI-armeabi-v7a but the PJSIP library didn't build successfully for this architecture.
Hence the pjsua application also could not be compiled.


It would be really helpful if we could get some guidance/help to move forward in development.Please let me know.


Thanks & Regards,

Monica M


_______________________________________________
Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@xxxxxxxxxxxxxxx
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org




_______________________________________________
Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@xxxxxxxxxxxxxxx
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org


_______________________________________________
Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@xxxxxxxxxxxxxxx
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org



_______________________________________________
Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@xxxxxxxxxxxxxxx
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux