06-20-2012 09:37 PM - edited 06-20-2012 09:41 PM
I'm trying to run three of the Cascades demos on the DevAlpha device. I can build the projects to the device, but I just get this error for all of them when they start up:
ldd:FATAL: Could not load library libQtDeclarative.so.4
I'm using the 10.0.4-beta BB10 NDK.
The demos are:
Solved! Go to Solution.
07-30-2012 04:31 PM - edited 07-30-2012 04:33 PM
Okay.... so now its working. In Momentics I had a target set up at 169.254.57.121 because thats what came up from auto-discover at one point when I was back on 10.0.4. I just deleted it and did auto-discover again and it used 169.254.0.1.
When it was on *.57.121 it was still connecting and installing the application, but gave this libQtDeclarative error. After switching to *.0.1 it connects, installs and runs the application fine.
07-31-2012 03:20 PM
Here's what we figured out:
Despite having the correct LD_LIBRARY_PATH in your bar-descriptor.xml this is what the BAR in your project has in MANIFEST.MF:
Entry-Point: LD_LIBRARY_PATH=app/native/lib app/native/HelloVideoCamera
And if we build it with the latest tools, MANIFEST.MF has:
Entry-Point: LD_LIBRARY_PATH=app/native/lib:/usr/lib/qt4/lib app/native/HelloVideoCamera
So you've still got some sort of tooling problem on your end. Which version do you have installed? It almost seems like you're compiling with the R4 or 2.0 NDK somehow.
06-21-2012 04:44 PM
You could try one of these:
* Ensure that the "bar-descriptor.xml" file has the following environment variable (you can view it on the IDE too; right click-> Open with -> Text Editor:
<env var="LD_LIBRARY_PATH" value="app/native/lib:/usr/lib/qt4/lib" />
* Ensure that the library is actually present on the device and on the correct path (you can SSH to the device):
# pwd /usr/lib # find .|grep QtDec ./qt4/lib/libQtDeclarative.so ./qt4/lib/libQtDeclarative.so.4 ./qt4/lib/libQtDeclarative.so.4.8 ./qt4/lib/libQtDeclarative.so.4.8.0 #
* If the library is just missing (or a different version one) on the device, you can try to reinstall the device image through the desktop software (however, it might still be a work in progrss for letting you re-install the BlackBerry Dev Alpha build). If you think the device has the libraries fin
Let us know any of this helps and feel free to ask away if you have any questions!
06-21-2012 08:35 PM
Yea, the env var is there in the descriptor, and the libraries are there on the device =\
$ pwd /usr/lib $ ls -ails qt4/lib/libQtDeclarative.so* 1425 1 lrwxrwxrwx 1 root nto 25 Apr 26 13:51 qt4/lib/libQtDeclarative.so -> libQtDeclarative.so.4.8.0 1426 1 lrwxrwxrwx 1 root nto 25 Apr 26 13:51 qt4/lib/libQtDeclarative.so.4 -> libQtDeclarative.so.4.8.0 1427 1 lrwxrwxrwx 1 root nto 25 Apr 26 13:51 qt4/lib/libQtDeclarative.so.4.8 -> libQtDeclarative.so.4.8.0 1810 5662 -rwxr-xr-x 1 root nto 2898708 Apr 15 09:48 qt4/lib/libQtDeclarative.so.4.8.0
06-21-2012 08:44 PM - edited 06-22-2012 11:46 AM
Trying to connect with the desktop manager just says it failed, and gives me the options to repair or retry. If I select repair then the device reboots while it says checking for updates, but then still fails when it boots back up. I can connect with ssh (clearly, above) and the QDE though. I think I remember desktop manager needing up update yesterday. I could be mistaken but I think it connected okay before the update.
Is there another way to reinstall the OS besides desktop manager?
BTW, I did a security wipe on the device to reset what I could, and now connecting the device keeps trying to install drivers but never completes. I'll try just reinstalling the desktop manager tonight.
06-22-2012 03:14 PM
Ouch. So it seems like you might be among the very few unlucky ones who had a different OS image, which seems incompatible against the public SDK, at least for Qt apps (as you can imagine, there were quite a few Dev Alphas going out to the public devs). Can you please share what the OS/build/version number on your device is shown to be?
And yes, at this moment, trying to get the OS image re-installed is probably the only solution. However, it seems that the current bundled of DTM 7.1 has a bug (the one you mentioned).
Good news is: The bundle 27 for DTM 7.1 should be coming out within a week and hopefully your problem should go away (i.e. you should be able to install the OS image). In the mean time, you can try reinstalling the desktop software and giving it a couple of more times if you wish.
Please bare with us through these inconveniences! I know it must be quite annoying when your code/app is ready but you can't make it run But you are almost there!
06-22-2012 05:21 PM
Forgot to add:
You could also try to run the applications on the simulator too, ofcourse. It should be compatible to the public SDK:
06-26-2012 11:11 AM
06-27-2012 12:00 PM
Any luck with trying to reinstall the device OS?
You can also try the following:
* Ensure that there is only ONE BlackBerry SDK installed (i.e. no other PlayBook tablet OS SDK installed alongside BlackBerry 10.0.04 SDK). Perhaps you can install them all and install only the BlackBerry 10 beta one; launch it through "bbndk.bat" (which sets up your PC's environment variables etc). Sometimes, having multple SDK's installed could potentially get things confused (although, that is very rare).
* Try to make a new app from scratch, through the IDE, after it was installed properly (as opposed to using some of the bundled sample apps or sample apps from github).
06-27-2012 12:32 PM - edited 06-27-2012 12:35 PM