03-10-2012 04:36 AM
Hi, sorry if this has been covered somewhere but I can't seem to find any information about it.
I have several large projects (games) I would like to port to the playbook. Large as in a few hundred MB of data (graphics, audio, etc).
What is the best way of handling this? I hope I don't have to deploy all that data every time I deploy another build to my device? Is the deploy system sophisticated enough to only copy files that have changed? How about for the simulator?
03-11-2012 10:19 AM
03-12-2012 01:42 PM
What IDE has atm is the ability to deploy your assets on the first run and then change to uploading binary only on consequtive runs.
Let me know if you have further questions/issues/suggestions on this topic.
03-12-2012 01:45 PM
03-12-2012 01:55 PM
There are docs about "patching" the installation but it only covers basic topics.
If you want to transfer files in app folder you have to make sure app installed in app dev mode
(in IDE if you just "run" it will be in this mode)
Then you have few options:
- if this is only binary that changes, you can use Upload tab checkbox
- you can transfer any file using Target File System Naigator view in IDE (drag & drop)
- create Qnx File Transfer launch configuration, and will tranfer select set of files on "launch"
- if you do it very often you can combine file transfer & regular run launch into Group launch configuration
If you use command line tools you can either use scp tool or blackberry-deploy -putFile
03-12-2012 02:02 PM
So, assets are generally things that are listed under Assets tab in your bar-descriptor.xml. Something like this in the source code of your bar-descriptor :
Now, in terms of a QT app. Do you link it statically? If so, you will loose time every time you upload the qt binary.
03-12-2012 04:46 PM
03-12-2012 05:57 PM
Well, this solves our problem then.
The idea behind "upload binary only" is to leave the "assets" unchanged and not copy them over every time as assets are typically your biggest files.
So, in case of Qt libraries - once you deploy them once, there is no need to change them. Hence what you can do in your case - (and say you have a clean device or you had to manually wipe the app) selec "Install application from a BAR file" on your first run, and then set it to "Only upload binary into existing installation".
Let me know if you have further issues with this.
03-12-2012 06:00 PM
03-12-2012 06:14 PM
Yes, my apologies, I missed this point.
Let me check with my collegues tomorrow - there should be a place on the system where we can place the Qt libraries and modify your path. This way you'll be able to upload the assets without reuploading the libraries.
This will be a tempraray workaround though. At some point Qt libraries should be available at usr/lib.