I was initially thinking about a transparent way that doesn't require class
loaders. Putting the .so file in the expansion alone would be a lot of help
already. It sizes about 16 megabytes when zipped (per architecture).

Take a look at this scenario:
1- In the main activity of our app extract the *libxwalkcore.sofile
*to  *'/data/data/"
+ context.getPackageName() + "/files/" + "libxwalkcore.so"'*
2- Set the file permissions to *execuatable* and *readonly*.
2- point the xwalk to use that native files instead of the default path.

I noticed something within *XWalkViewDelegate.java -> loadXWalkLibrary() *where
the .so file is being checked. Any way for us to expose that without
changing your code? Because this would be the easiest way to handle the
size without actually modifying the code.

The *System.load() *simply needs to look for it in another path.

I look forward to your input on this.

Also, if you need a hand let us know.

Thanks.

Best Regards,
Aram

On Fri, May 15, 2015 at 2:19 PM, Staudinger, Robert <
[email protected]> wrote:

> Lin, what do you think?
>
> Would it be feasible to attach a shared crosswalk apk as an expansion
> file, and re-use most of the shared-crosswalk loader to instantiate
> it? This issue has been requested a few times and we might have most
> of the infrastructure in place now
> https://crosswalk-project.org/jira/browse/XWALK-2618
>
> Thanks,
> Rob
>
>
> On 14 May 2015 at 18:22, Aram Azhari <[email protected]> wrote:
> > Could you be a bit more specific?
> >
> > I have added the .so native library to the obb and on my activity I'm
> > extracting that to app's private storate under
> > '/data/data/com.mypackage.myappname/files/arm/libxwalkcore.so
> >
> > So now I want to make sure that xwalk is loading that file instead of the
> > one in the default path.
> >
> > Unfortunately there are no documentation on this.
> >
> > Also, I'm seeing that in commit 9c144896c38da510ae25cf2d3705b65b408af14d
> > [9c14489] a file was added called XWalkLibraryLoader.java .
> >
> > So I'm wondering how this can be done.
> >
> > Note: I'm currently using my own activity and load xwalk as a
> > dialogfragment.
> >
> > I would appreciate it if you could guide me on this.
> >
> > Thank you.
> >
> > On Wed, May 13, 2015 at 3:27 PM, Staudinger, Robert
> > <[email protected]> wrote:
> >>
> >> Hi Aram,
> >>
> >> you could look into putting crosswalk into an expansion file, and
> >> loading it from there. The classloader instantiating crosswalk has
> >> been enhanced lately to support shared crosswalk, you could probably
> >> take advantage and use the same approach, possibly with relatively
> >> moderate modifications.
> >>
> >> Best,
> >> Rob
> >>
> >> On 13 May 2015 at 20:40, Aram Azhari <[email protected]> wrote:
> >> > Hi,
> >> >
> >> > I would like to know if the crosswalk embedded can be actually
> >> > downloaded
> >> > separately (perhaps through a downloader service) and then dynamically
> >> > be
> >> > loaded into my app?
> >> >
> >> > My application is not based on xwalk entirely, but I hit the size
> limit
> >> > of
> >> > googleplay and I don't want the user to install a separate app for
> >> > xwalk.
> >> > I'm thinking something like dynamically loading the libraries that
> were
> >> > downloaded.
> >> >
> >> > Has anybody ever done this? or do you have any suggestions?
> >> >
> >> > Thanks.
> >> >
> >> > Aram
> >> >
> >> > _______________________________________________
> >> > Crosswalk-help mailing list
> >> > [email protected]
> >> > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
> >> >
> >>
> >>
> >>
> >> --
> >> Intel GmbH - Registergericht Muenchen HRB 47456 - Dornacher Strasse 1,
> >> 85622 Feldkirchen, Germany
> >
> >
> >
> >
> > --
> >
> > Best Regards
> > Aram Azhari
>
>
>
> --
> Intel GmbH - Registergericht Muenchen HRB 47456 - Dornacher Strasse 1,
> 85622 Feldkirchen, Germany
>



-- 

Best Regards
Aram Azhari
_______________________________________________
Crosswalk-help mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help

Reply via email to