To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70166 Issue #|70166 Summary|prune textenc bloat Component|porting Version|680m185 Platform|All URL| OS/Version|Linux Status|NEW Status whiteboard| Keywords| Resolution| Issue type|PATCH Priority|P3 Subcomponent|code Assigned to|mba Reported by|mmeeks
------- Additional comments from [EMAIL PROTECTED] Fri Oct 6 12:59:49 -0700 2006 ------- So cloned this part of the discussion from i#60696, > A small test on Windows revealed that after removing all textenc functions > from the export and the textenc.lib from the makefile map the following > symbols show up as unresolved: Ah - so tooling is everything ;-) if you poke at http://go-oo.org/ooo-build/bin/oosize - there is a (Linux only) tool that shows object size breakdown by source directory: eg. you can look at 'svx' and say: wow that is a big pile of code, then break it down by source directory and source file to find the offendors (some of which are quite suprising); anyhow it shows: [EMAIL PROTECTED]:/opt/OpenOffice/ood680-m4/sal/textenc> /opt/OpenOffice/HEAD/bin/oosize --ls Found module '/data/OpenOffice/ood680-m4/sal' Size breakdown context.c 664 tenchelp.c 1036 unichars.c 1064 textcvt.c 1128 converter.c 1144 convertsinglebytetobmpunicode.cxx 1244 converteuctw.c 2140 convertgb18030.c 2176 tcvtutf8.c 2176 convertiso2022kr.c 2316 convertiso2022jp.c 2340 convertbig5hkscs.c 2420 tcvtutf7.c 2428 tcvtmb.c 2728 convertiso2022cn.c 3472 tcvtbyte.c 3672 tencinfo.c 9108 textenc.cxx 1490820 so - as you see, 1 file is a huge proportion of the problem here; luckily that file exports only 1 symbol ;-) ImplTextEncodingData const * Impl_getTextEncodingData(rtl_TextEncoding nEncoding) By commenting out the contents of that I get: 1797832 ../../unxlngi6.pro.before/lib/libuno_sal.so 273544 libuno_sal.so # after So - AFAICS this is really the obvious place to cut to loose 85% of the code at a single stroke ;-) [ of course, we'd prolly need to re-instate / in-line at least some of the common ASCII / common Win32 code-page / UTF8 stuff ] but it should be fairly trivial to save a nice whack of code there in the common case. I'm even interested enough to have a go myself now ;-) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
