Hi Robert,
See my comments below. -----Original Message----- From: Staudinger, Robert [mailto:[email protected]] Sent: Friday, March 27, 2015 7:27 PM To: Huo, Halton Cc: Dong, Jun; Balestrieri, Francesco; <crosswalk-dev@lists. org> Subject: Re: [Crosswalk-dev] Intent to Implement: LZMA support for Crosswalk Halton, I have two questions about this: On 27 March 2015 at 12:15, Huo, Halton <[email protected]<mailto:[email protected]>> wrote: > +1 for Francesco’s idea about building out lzma and non-lzma support > together and let app developer choose which to use. 1. Will the deflated library be stored on disk? That would only give the startup penalty on first launch, at the expense of needing more space. Yes, decompressing will take some time, and we have 2 library(decompressed in lib directory, and the compressed in apk). However, due to the Android’s limitation, we can’t delete the compressed one(because it resides in an signing package). > As for how to release them, my suggestion is to combine lzma and > non-lzma in make_apk zip, while separate zip for webview and cordova. > Which the release folder will be looked like: 2. Do you think the packaging tools (make-apk, app-tools) could do the lzma step before creating the apk? Then we wouldn't have so many extra releases. OK, we can ship an uncompressed library with make_apk, and this will consume some more time for their first time to enable the ‘use_lzma’ flag. - Rob
_______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
