Crash due to localeconv?

Aleix Pol aleixpol at kde.org
Mon Nov 14 23:12:46 UTC 2016


On Mon, Nov 14, 2016 at 8:25 PM, Albert Astals Cid <aacid at kde.org> wrote:
> El dissabte, 12 de novembre de 2016, a les 0:24:59 CET, Aleix Pol va escriure:
>> Yes, I'm not sure how you're compiling the application, but you're
>> possibly not compiling the .mo files. If you use the tarballs (which
>> contain the .po files) you'll see them getting generated.
>
> Which kstars tarballs contain the .po files?
>
> Cheers,
>   Albert
>
>>
>> Aleix
>>
>> On Fri, Nov 11, 2016 at 7:26 PM, Jasem Mutlaq <mutlaqja at ikarustech.com>
> wrote:
>> > Don't we need to explicitly ship those files? I know that .po files are
>> > made into binary .mo, so we need to compile those for Android and install
>> > them to same location? KF5 will take care of loading the "correct" one
>> > depending on the Android locale? Is there documentation on this?
>> >
>> > On Fri, Nov 11, 2016 at 7:25 PM, Aleix Pol <aleixpol at kde.org> wrote:
>> >> It should work just as any other project that uses ki18n.
>> >>
>> >> Please test and open a new thread if it has problems.
>> >>
>> >> Aleix
>> >>
>> >> On Fri, Nov 11, 2016 at 4:31 PM, Jasem Mutlaq <mutlaqja at ikarustech.com>
>> >>
>> >> wrote:
>> >> > So it appears the localeconv was supported in API 21, so we'll just
>> >> > bump
>> >> > the
>> >> > API version to that. Another issue is localization support as we'd like
>> >> > to
>> >> > support multiple languages, how is that done exactly with Android?
>> >> >
>> >> > Regards,
>> >> > Jasem
>> >> >
>> >> > On Thu, Nov 10, 2016 at 6:31 PM, Aleix Pol <aleixpol at kde.org> wrote:
>> >> >> No, it shouldn't matter as long as when compiling you link against the
>> >> >> right set of libraries.
>> >> >>
>> >> >> I don't know what library it is, if it's looking for localeconv, I
>> >> >> guess localeconv.so or liblocaleconv.so?
>> >> >>
>> >> >> Aleix
>> >> >>
>> >> >> On Thu, Nov 10, 2016 at 4:22 PM, Jasem Mutlaq
>> >> >> <mutlaqja at ikarustech.com>
>> >> >>
>> >> >> wrote:
>> >> >> > How do we include the library in the APK exactly? And what library
>> >> >> > is
>> >> >> > exactly? We're using androiddeployqt
>> >> >> >
>> >> >> > I saw the gimp issue, and we can increase the API Level (which is
>> >> >> > set
>> >> >> > at
>> >> >> > 15
>> >> >> > now). but then we'd lose about 30% of the market (see
>> >> >> > https://developer.android.com/about/dashboards/index.html) so it
>> >> >> > would
>> >> >> > be
>> >> >> > better to resolve this and no there are no choices then we'd bump
>> >> >> > the
>> >> >> > API
>> >> >> > level. I'm using the latest NDK from Google but should that matter
>> >> >> > if
>> >> >> > the
>> >> >> > Target API Level is set to 15?
>> >> >> >
>> >> >> > On Thu, Nov 10, 2016 at 6:15 PM, Aleix Pol <aleixpol at kde.org> wrote:
>> >> >> >> Hi,
>> >> >> >> I haven't seen this error before, maybe the apk should include the
>> >> >> >> library?
>> >> >> >>
>> >> >> >> A fast search suggests that this is on API >=21.
>> >> >> >> https://github.com/Rupan/gmp/issues/6
>> >> >> >>
>> >> >> >> Maybe your application or Qt are compiled with a too new NDK
>> >> >> >> version?
>> >> >> >>
>> >> >> >> Aleix
>> >> >> >>
>> >> >> >> On Thu, Nov 10, 2016 at 9:46 AM, Jasem Mutlaq
>> >> >> >> <mutlaqja at ikarustech.com>
>> >> >> >>
>> >> >> >> wrote:
>> >> >> >> > Ok, could this be due perhaps to target API Level settings?
>> >> >> >> > Currently,
>> >> >> >> > we
>> >> >> >> > set it to 15. Should that be increased?
>> >> >> >> >
>> >> >> >> > On Thu, Nov 10, 2016 at 11:32 AM, Jasem Mutlaq
>> >> >> >> > <mutlaqja at ikarustech.com>
>> >> >> >> >
>> >> >> >> > wrote:
>> >> >> >> >> Hello,
>> >> >> >> >>
>> >> >> >> >> After submitting KStars Lite to the Google Play Store last week,
>> >> >> >> >> I've
>> >> >> >> >> been
>> >> >> >> >> getting this crash report:
>> >> >> >> >>
>> >> >> >> >> java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate
>> >> >> >> >> symbol
>> >> >> >> >> "localeconv" referenced by "libkstars.so"...
>> >> >> >> >> at java.lang.Runtime.loadLibrary(Runtime.java:364)
>> >> >> >> >> at java.lang.System.loadLibrary(System.java:526)
>> >> >> >> >> at
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> org.qtproject.qt5.android.bindings.QtLoader.loadApplication(QtLo
>> >> >> >> >> ader.java:244) at
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> org.qtproject.qt5.android.bindings.QtLoader.startApp(QtLoader.ja
>> >> >> >> >> va:647)
>> >> >> >> >> at
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> org.qtproject.qt5.android.bindings.QtActivityLoader.onCreate(QtA
>> >> >> >> >> ctivityLoader.java:181) at
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> org.qtproject.qt5.android.bindings.QtActivity.onCreate(QtActivit
>> >> >> >> >> y.java:269)
>> >> >> >> >> at android.app.Activity.performCreate(Activity.java:5459)
>> >> >> >> >> at
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> android.app.Instrumentation.callActivityOnCreate(Instrumentation
>> >> >> >> >> .java:1093)
>> >> >> >> >> at
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> android.app.ActivityThread.performLaunchActivity(ActivityThread.
>> >> >> >> >> java:2364)
>> >> >> >> >> at
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> android.app.ActivityThread.handleLaunchActivity(ActivityThread.j
>> >> >> >> >> ava:2458)
>> >> >> >> >> at
>> >> >> >> >> android.app.ActivityThread.access$900(ActivityThread.java:172)
>> >> >> >> >> at
>> >> >> >> >>
>> >> >> >> >> android.app.ActivityThread$H.handleMessage(ActivityThread.java:1
>> >> >> >> >> 305)
>> >> >> >> >> at android.os.Handler.dispatchMessage(Handler.java:102)
>> >> >> >> >> at android.os.Looper.loop(Looper.java:146)
>> >> >> >> >> at android.app.ActivityThread.main(ActivityThread.java:5598)
>> >> >> >> >> at java.lang.reflect.Method.invokeNative(Native Method)
>> >> >> >> >> at java.lang.reflect.Method.invoke(Method.java:515)
>> >> >> >> >> at
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(Zygot
>> >> >> >> >> eInit.java:1283) at
>> >> >> >> >> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1099)
>> >> >> >> >> at dalvik.system.NativeStart.main(Native Method)
>> >> >> >> >>
>> >> >> >> >> Anyone know how to resolve this for Qt/KDE apps?
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Best Regards,
>> >> >> >> >> Jasem Mutlaq
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Best Regards,
>> >> >> >> > Jasem Mutlaq
>> >> >> >
>> >> >> > --
>> >> >> > Best Regards,
>> >> >> > Jasem Mutlaq
>> >> >
>> >> > --
>> >> > Best Regards,
>> >> > Jasem Mutlaq
>> >
>> > --
>> > Best Regards,
>> > Jasem Mutlaq
>
>

I assumed, correct me if I'm wrong. I guess it's in the big .po
archive for KDE Applications?

Aleix


More information about the KDE-Android mailing list