On Mon, Aug 14, 2017 at 12:43 PM, Otavio Salvador <[email protected]> wrote: > Hello everyone, > > On Mon, Aug 14, 2017 at 4:38 PM, Andreas Müller > <[email protected]> wrote: >> On Mon, Aug 14, 2017 at 4:10 PM, Andreas Müller >> <[email protected]> wrote: >>> On Mon, Aug 14, 2017 at 12:22 PM, Jussi Kukkonen >>> <[email protected]> wrote: >>>> >>>> >>>> I chatted with rakuco who's done nice work with up to date chromium in >>>> meta-crosswalk, he's got some relevant commits related to this: >>>> >>>> https://github.com/rakuco/meta-crosswalk/commit/5aae1539c3d62b295dba40f494397c0797140b0f >>>> https://github.com/rakuco/meta-crosswalk/commit/c56aa2bf047d3a01e14f4f9bfe5f88664b333f36 >>>> >>>> On a related note, this good work is currently a bit hidden in >>>> meta-crosswalk -- is there a chance we could get this combined with >>>> meta-browser (or whatever place makes sense)? I know next to nothing about >>>> chromium packaging so CCing Raphael and the meta-browser maintainers for >>>> comments. >>>> >>> That is interesting. If your suspicion is correct, we are very close >>> to the edge of file working properly or not. With meta-browser >>> c79cf6c7811afd2cd167e8967e3c29b1e797371e (16 commits behind master) I >>> get a proper detected and then split chromium. With meta-browser >>> master head file incorrectly reports that chrome is split already. I >>> did not check the exact size numbers but my file browser reports 4.3G >>> for both cases. >>> >>> Just to gather further information I think about bisecting meta-browser. >>> >> After first bisect build I checked size:: 4299018288 bytes / 2^32 is >> 4294967296 - so no need for further bisecting. Thanks Jussi for the >> hint. >> >> For now I'll choose old version - have not much time to take care. > > Indeed it does sound like the proper workaround for now. That said, > I'd love to receive more help from meta-crosswalk people and avoid > duplication of work in packaging Chromium so I am adding Raphael on Cc > here so he can comment about how we can try to work together on this. >
Please add below to CHROMIUM_EXTRA_ARGS symbol_level=1 Thats enough to create legible stack traces. and if size is still large then add remove_webcore_debug_symbols=true blink is the biggest contributor to debug info. I think this should suffise. and there is no need to do it for 32bit and not for 64bit just make it same for all arches. -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
