On Fri, Mar 22, 2013 at 12:39 PM, Rusty Lynch <[email protected]> wrote:
> On 03/22/2013 06:08 AM, Jan-Simon Möller wrote: > >> On Friday 22 March 2013 09:09:07 Gustavo Sverzut Barbieri wrote: >> >>> particularly for linking, it will likely swap like crazy with less than >>> 8Gb >>> >> Wow ... 8GB RAM needed to link this beast ? What about splitting it into >> smaller pieces ? >> > > Thats a great suggestion for the webkit project. The codebase is larger > then most operating systems. that's already the case, but just used during development. Traditionally webkit produces couple of static libraries (.a) such as javascript, webcore... then link them all into the resulting dynamic library libwebkit-port.so (names vary). with webkit-efl we have the "shared-core" concept that just creates dynamic libraries for everything. Then if you just modify the top level layer (webkit-efl) the underlying (js, webcore) are untouched. This comes with a runtime penalty, but works for development -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: [email protected] Skype: gsbarbieri Mobile: +55 (19) 9225-2202
_______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
