Hi,
I'm working on Crosswalk integration on Tizen IVI. I've made a quick study about crosswalk memory footprint. I've tried to use the maximum of Tizen available dependencies instead of 3rd party ones. Atm I'm able to use the below Tizen depedencies thanks to the use_system_xxx build flags and python script (./src/build/linux/unbundle/replace_gyp_files.py) : - flac - harfbuzz - libevent - libjpeg - libpng - libvpx - speex - libusb - openssl I get a 'poor' gain of 1684 Bytes on disk space and nothing (less than 1 MB over 135 MB) on RAM footprint. Then there are some 3rd party deps without use_system_xxx build flag (like mesa), I suppose that is volunteer to not let the user chooses those external deps... Before deeply digging into this, I'm wondering whether someone has already thought at this and could share information. The point is to reduce memory footprint and so duplicated packages in Tizen, brought by Crosswalk 3rd party deps. We could either apply chromium patches to Tizen deps or replace Tizen packages by Crosswalk 3rd party package... Any opinions on this topic is welcomed. Thanks and regards, Corentin _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
