On Fri, 2011-07-15 at 12:29 +0200, Lubos Lunak wrote:
is there really supposed to be one CppunitTest*mk per
unittest? This way module toplevel directories are going to be full of these
files if we one day get to having a decent unittest coverage.
Well, one .mk per output test library anyway seems to be the way the
gbuild stuff works. No particular requirement to have one lib per unit
test in general, especially if you think of each CPPUNIT_TEST as the
actual unit test, and so bundle them into a minimum of output libs.
e.g. currently there are only two test libraries generated in sw, one
that needs to poke at the internal non-exported api which requires the
link to the .o's of the libsw (shudder) and one that needs to poke at
the external exported api which can link to libsw "normally".
C.
Context
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.