Android asset support/deployment advice needed

[BogDan]

Hi Niko,

This is the idea behind first option, to use the same DEPLOYMENT variable as Symbian to install (copy to assets) your application files, even more, it will be nice if your target/libs can be installed (copy to libs/armeabi(-v7a)) by the same tool (make).

Of course, you'll need to change some .pro files and to create .apk by yourself, if you don't want to use QtCreator.

Cheers,
BogDan.  




----- Original Message -----
> From: Niko Sams <niko.sams at gmail.com>
> To: BogDan <bog_dan_ro at yahoo.com>
> Cc: "necessitas-devel at kde.org" <necessitas-devel at kde.org>; "alessandro.portale at nokia.com" <alessandro.portale at nokia.com>
> Sent: Monday, June 27, 2011 5:08 PM
> Subject: Re: Android asset support/deployment advice needed
> 
> On Mon, Jun 27, 2011 at 11:41, BogDan <bog_dan_ro at yahoo.com> wrote:
>>  Hello,
>> 
>> 
>>  I'm trying to finish the implementation for android assets deployment 
> support, and I found that
>>  in QtCreator are two ways to handle it:
>> 
>>  1  - add a new step to deployment, this step will run " make 
> INSTALL_ROOT="your_android_folder" install " command  to copy all 
> application data to your android/assets folder, this step can also copy all libs 
> to android/libs folder, so we can remove most of 
> "AndroidPackageCreationStep::createPackage".
>> 
>>  2 - parse 
> "qt4Target()->qt4Project()->rootProjectNode()->installsList()" 
> and copy all files to android/assets folder.
>> 
>> 
>>  I almost finished first approach, and I want to ask you if this is the 
> right way to do it or should I switch to second one.
>> 
> 
> please make it possible to use from the commandline. I'd like to have
> the choice to use another IDE.
> Symbian uses DEPLOYMENT for that, something similar would make sense I think.
> 
> Niko
>