11-21-2012 10:12 AM
I can build and run an app that uses accelerometer on the actual device. .PRO file has CONFIG += mobility
and MOBILITY += sensors
Trying to simply build and run the app for the simulator produce the error about missing QtMobilitysimulator library.
I understand that accelerometer is useless on the simulator, but I would still like to build and run the app on the simulator for testing purposes.
Right now - that is impossible.
Am I missing something or - there is nothing that can be done except create two different build (with and without mobility libraries in).
Solved! Go to Solution.
11-21-2012 10:20 AM
11-21-2012 10:26 AM
I was not aware of it and I cannot find it withiin my SDK. Where would it be located?
More importantly ...
The problem we are having is building the app, not simulating sensors.
We cannot build the app at all for the simulator as soon as the parameters I outlined are set. Same works fine on a device.
11-21-2012 10:31 AM - edited 11-21-2012 10:34 AM
As for the controller please refer to: https://developer.blackberry.com/develop/simulator
As for building for the simulator without sensor support I addressed the question to our internal teams. Will update it you in short.
11-21-2012 10:51 AM
@klajili - Thank you for letting us know about the Controller app. When one installs the SDK on OSX - a link to the IDE and Simulator vmware files are created. I wonder why not a link to the "controller" app. That's why I missed it actually.
Btw. there is no need to browse the .vmware file to get to the controller (at least on OSX)
For anyone looking for a controller on OSX - it is located in the same folder as your ORIGINAL .vmware file for the simulator. You may be clicking on a link that was created during the install - you have to right click on it, show original and you will find the "controller" folder in there.
@xsacha - I am aware that I could use the conditionals to create a different build. In my original post I asked if I have to use a different build or if there was a way to actually solve the problem. Thanks for the suggestion though.
Since there is a controller app - I now see that it possible to simulate a whole range of sensors within the simulator which is great, but - unusible unless I can link the QtMobilitySimlator library so hopefully @klajili will be able to provide an answer on how to build.
11-21-2012 11:06 AM - edited 11-21-2012 11:06 AM
Well Simulator is going to be a separate build anyway (since it's x86) so the conditions won't change anything there unless your app depends on it.
But if you want to test the sensors, QtMobilitySimulator is not what you'd want to use as it assumes you have no sensors (and it is designed for Qt Simulator which we don't use), So you would want to use just the normal sensor includes.
11-21-2012 01:21 PM
What are the "normal" sensor includes and, more importantly, why are the ones we use "abnormal"?
Could you please elaborate - I seem to be missing something important here.
11-21-2012 10:58 PM
I think we are talking about different things. Include headers are one thing, linking libraries are another. I am talking about libraries being linked here. This is autmatically selected based on your .pro configuration (among other things).