On Tuesday 17 of April 2012, Stephan Bergmann wrote:
On 04/16/2012 06:23 PM, Lubos Lunak wrote:
On Monday 16 of April 2012, Michael Meeks wrote:
Oh - and finally (Lubos) I pushed an item to the ESC agenda to discuss
whether we should be exposing tons of classes and their symbols in the
product, just to make unit tests work :-)
I assume this is about 69d46dd7a6adfffd71da055bb65108c80d27395f .
Would it be possible to replace gb_CppunitTest_add_library_objects with
something that explicitly lists (only) the individual objects from the
given library that should be linked into the test?
I doubt that would work with an application, where presumably everything is
eventually used by everything else.
But maybe gbuild could be changed to include target-specific LDFLAGS? That
way it'd be possible to build as 'make sc_ucalc_LDFLAGS=-Wl,--strip-all' .
Probably even Bjoern's --enable-debug extension can do.
--
Lubos Lunak
l.lunak@suse.cz
Context
Re: Automatic using ::rtl::OUString etc. · Lubos Lunak
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.